Setup of multiple IOT networks devices

ABSTRACT

The present disclosure relates to setup of IoT network devices, and specifically to setup of multiple similar IoT devices at substantially the same time using joint authentication. Embodiments include, for example, receiving, at an existing network device on a network, one or more communications, wherein the one or more communications include an indication that multiple new network devices are associated with the network; receiving an indication that the multiple new network devices have generated a setup access point; establishing a connection with the access point of each of the multiple new network devices; receiving identification information, wherein the identification information includes information identifying each of the multiple new network devices; and transmitting the identification information identifying each of the multiple new network devices, wherein when the identification information is received, the identification information facilitates generating an authentication query to authenticate one or more of the multiple new network devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.14/947,697, filed on Nov. 20, 2015, which is a continuation of U.S.application Ser. No. 14/455,940 filed Aug. 10, 2014, now issued as U.S.Pat. No. 9,451,462. This application is also a continuation-in-part ofU.S. application Ser. No. 14/947,001 filed on Nov. 20, 2015, which is acontinuation of U.S. application Ser. No. 14/455,940 filed on Aug. 10,2014, now issued as U.S. Pat. No. 9,451,462. This application is also acontinuation-in-part of U.S. application Ser. No. 15/217,118 filed onJul. 22, 2016 which is a continuation of U.S. application Ser. No.14/529,745, now issued as U.S. Pat. No. 9,426,153, which is acontinuation of U.S. application Ser. No. 14/479,545 filed on Sep. 8,2014, now issued as U.S. Pat. No. 9,210,192. This application is also acontinuation-in-part of U.S. application Ser. No. 14/946,348 filed onNov. 19, 2015. This application is also a continuation-in-part of U.S.application Ser. No. 14/946,308 filed on Nov. 19, 2015, which is acontinuation of U.S. application Ser. No. 14/462,725 filed on Aug. 19,2014. This application is also a continuation-in-part of U.S.application Ser. No. 14/946,290 filed on Nov. 19, 2015 which is acontinuation of U.S. application Ser. No. 14/454,163 filed on Aug. 7,2014. This application is also a continuation-in-part of U.S.application Ser. No. 14/455,938 filed on Aug. 10, 2014. This applicationis also a continuation-in-part of U.S. application Ser. No. 14/242,806filed on Apr. 1, 2014. All of these applications are hereby incorporatedby reference in their entireties for all purposes.

FIELD

The present disclosure relates to setup of multiple IoT network devices.Specifically, various techniques and systems are provided for setup ofmultiple similar IoT devices at substantially the same time using jointauthentication.

BRIEF SUMMARY

Embodiments of the present invention are directed to acomputer-implemented method. The method includes receiving, at anexisting network device on a network, one or more communications,wherein the one or more communications include an indication thatmultiple new network devices are associated with the network; receivingan indication that the multiple new network devices have each generateda setup access point; establishing a connection with the setup accesspoint of each of the multiple new network devices; receivingidentification information, wherein the identification informationincludes information identifying each of the multiple new networkdevices; and transmitting the identification information identifyingeach of the multiple new network devices, wherein when theidentification information is received, the identification informationfacilitates generating one or more authentication queries toauthenticate one or more of the multiple new network devices.

Alternative embodiments of the present invention are directed to acomputing device. The computing device includes one or more processors,and a memory having instructions stored thereon, which when executed bythe one or more processors, cause the computing device to performoperations. The operations include receiving, at an existing networkdevice on a network, one or more communications, wherein the one or morecommunications include an indication that multiple new network devicesare associated with the network; receiving an indication that themultiple new network devices have each generated a setup access point;establishing a connection with the setup access point of each of themultiple new network devices; receiving identification information,wherein the identification information includes information identifyingeach of the multiple new network devices; and transmitting theidentification information identifying each of the multiple new networkdevices, wherein when the identification information is received, theidentification information facilitates generating one or moreauthentication queries to authenticate one or more of the multiple newnetwork devices.

Alternative embodiments of the present invention include anon-transitory computer-readable storage medium having instructionsstored thereon, which when executed by a computing device, cause thecomputing device to receive, at an existing network device on a network,one or more communications, wherein the one or more communicationsinclude an indication that multiple new network devices are associatedwith the network; receive an indication that the multiple new networkdevices have each generated a setup access point; establish a connectionwith the setup access point of each of the multiple new network devices;receive identification information, wherein the identificationinformation includes information identifying each of the multiple newnetwork devices; and transmit the identification information identifyingeach of the multiple new network devices, wherein when theidentification information is received, the identification informationfacilitates generating one or more authentication queries toauthenticate one or more of the multiple new network devices.

This summary is not intended to identify key or essential features ofthe claimed subject matter, nor is it intended to be used in isolationto determine the scope of the claimed subject matter. The subject mattershould be understood by reference to appropriate portions of the entirespecification of this patent, any or all drawings, and each claim.

The foregoing, together with other features and embodiments, will becomemore apparent upon referring to the following specification, claims, andaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the following drawing figures:

FIG. 1 illustrates an example of a wireless network environment,according to embodiments of the present invention.

FIG. 2 is a flowchart illustrating an embodiment of a process forregistering one or more network devices, according to embodiments of thepresent invention.

FIG. 3 illustrates an example of a network environment, according toembodiments of the present invention.

FIG. 4 illustrates an example of a network environment, according toembodiments of the present invention.

FIG. 5 illustrates an example of a network environment, according toembodiments of the present invention.

FIG. 6 illustrates an example of a local area network including agateway and three network devices, according to embodiments of thepresent invention.

FIG. 7 illustrates an example of a local area network including agateway, according to embodiments of the present invention.

FIG. 8 illustrates an example of a local area network including agateway and a network device connected to three new network devices,according to embodiments of the present invention.

FIG. 9 illustrates an example of a local area network including agateway and a network device connected to three new network devices andan access device, according to embodiments of the present invention.

FIG. 10 illustrates an example of a local area network including agateway and six network devices, according to embodiments of the presentinvention.

FIG. 11 illustrates an example of a local area network including agateway and six network devices, according to embodiments of the presentinvention.

FIG. 12 illustrates an example of a local area network including agateway and three network devices, according to embodiments of thepresent invention.

FIG. 13 illustrates an example of a local area network including agateway and three devices connected to the gateway, according toembodiments of the present invention.

FIG. 14 illustrates a house with two rooms and network devices in eachroom, according to embodiments of the present invention.

FIG. 15 illustrates an example of a local area network including agateway and three network devices each connected to a new networkdevice, according to embodiments of the present invention.

FIG. 16 illustrates an example of a local area network including agateway and three network devices each connected to a new network deviceand one network device connected to an access device, according toembodiments of the present invention.

FIG. 17 illustrates an example of a local area network including agateway and a network device each connected to three new network devicesin a chain, according to embodiments of the present invention.

FIG. 18 illustrates an example of a local area network including agateway and a network device each connected to an access device andthree new network devices in a chain, according to embodiments of thepresent invention.

FIG. 19 illustrates an exemplary user interface display for anapplication on an access device, according to embodiments of the presentinvention.

FIG. 20 illustrates an exemplary user interface display for anapplication on an access device, according to embodiments of the presentinvention.

FIG. 21 is a flow chart showing an exemplary process for a network toautomatically select grouping for network devices on a network,according to embodiments of the present invention. according toembodiments of the present invention.

FIG. 22 illustrates an example of a front view of a network device,according to embodiments of the present invention.

FIG. 23 illustrates an example of a side view of a network device,according to embodiments of the present invention.

FIG. 24 illustrates an example of a block diagram of a network device,according to embodiments of the present invention.

FIG. 25 illustrates a block diagram illustrating an example of an accessdevice, according to embodiments of the present invention.

FIG. 26 illustrates a block diagram illustrating an example of a server,in accordance with some embodiments.

FIG. 27 illustrates a block diagram illustrating an example of agateway, in accordance with some embodiments.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

The ensuing description provides exemplary embodiments only, and is notintended to limit the scope, applicability, or configuration of thedisclosure. Rather, the ensuing description of the exemplary embodimentswill provide those skilled in the art with an enabling description forimplementing an exemplary embodiment. It should be understood thatvarious changes may be made in the function and arrangement of elementswithout departing from the spirit and scope of the invention as setforth in the appended claims.

Specific details are given in the following description to provide athorough understanding of the embodiments. However, it will beunderstood by one of ordinary skill in the art that the embodiments maybe practiced without these specific details. For example, circuits,systems, networks, processes, and other components may be shown ascomponents in block diagram form in order not to obscure the embodimentsin unnecessary detail. In other instances, well-known circuits,processes, algorithms, structures, and techniques may be shown withoutunnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartmay describe the operations as a sequential process, many of theoperations can be performed in parallel or concurrently. In addition,the order of the operations may be re-arranged. A process is terminatedwhen its operations are completed, but could have additional steps notincluded in a figure. A process may correspond to a method, a function,a procedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination can correspond to a return of thefunction to the calling function or the main function.

The term “machine-readable storage medium” or “computer-readable storagemedium” includes, but is not limited to, portable or non-portablestorage devices, optical storage devices, and various other mediumscapable of storing, containing, or carrying instruction(s) and/or data.A machine-readable medium may include a non-transitory medium in whichdata can be stored and that does not include carrier waves and/ortransitory electronic signals propagating wirelessly or over wiredconnections. Examples of a non-transitory medium may include, but arenot limited to, a magnetic disk or tape, optical storage media such ascompact disk (CD) or digital versatile disk (DVD), flash memory, memoryor memory devices. A computer-program product may include code and/ormachine-executable instructions that may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a class, or any combination of instructions, datastructures, or program statements. A code segment may be coupled toanother code segment or a hardware circuit by passing and/or receivinginformation, data, arguments, parameters, or memory contents.Information, arguments, parameters, data, etc. may be passed, forwarded,or transmitted via any suitable means including memory sharing, messagepassing, token passing, network transmission, etc.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessary tasks.

Systems depicted in some of the figures may be provided in variousconfigurations. In some embodiments, the systems may be configured as adistributed system where one or more components of the system aredistributed across one or more networks in a cloud computing system.

A network may be set up to provide an access device user with access tovarious devices connected to the network. For example, a network mayinclude one or more network devices that provide a user with the abilityto remotely configure or control one or more electronic devices (e.g.,appliances) within an environment that can support the network. Anenvironment can include, for example, a home, an office, a business, anautomobile, a park, or the like. A network may include one or moregateways that allow client devices (e.g., network devices, accessdevices, or the like) to access the network by providing wiredconnections and/or wireless connections using radio frequency channelsin one or more frequency bands. The one or more gateways may alsoprovide the client devices with access to one or more external networks,such as a cloud network, the Internet, and/or other wide area networks.

A local area network, such as a user's home local area network, caninclude multiple network devices that provide various functionalities.Network devices may be accessed and controlled using an access deviceand/or one or more network gateways. One or more gateways in the localarea network may be designated as a primary gateway that provides thelocal area network with access to an external network. The local areanetwork can also extend outside of the user's home and may includenetwork devices located outside of the user's home. For instance, thelocal area network can include network devices such as exterior motionsensors, exterior lighting (e.g., porch lights, walkway lights, securitylights, or the like), garage door openers, sprinkler systems, or othernetwork devices that are exterior to the user's home. It is desirablefor a user to be able to access the network devices while located withinthe local area network and also while located remotely from the localarea network. For example, a user may access the network devices usingan access device within the local area network or remotely from thelocal area network.

In some embodiments, a user may create an account with login informationthat is used to authenticate the user and allow access to the networkdevices. For example, once an account is created, a user may enter thelogin information in order to access a network device in a logicalnetwork.

In some embodiments, an accountless authentication process may beperformed so that the user can access one or more network devices withina logical network without having to enter network device logincredentials each time access is requested. While located locally withinthe local area network, an access device may be authenticated based onthe access device's authentication with the logical network. Forexample, if the access device has authorized access to the logicalnetwork (e.g., a WiFi network provided by a gateway), the networkdevices paired with that logical network may allow the access device toconnect to them without requiring a login. Accordingly, only users ofaccess devices that have authorization to access the logical network areauthorized to access network devices within the logical network, andthese users are authorized without having to provide login credentialsfor the network devices.

An accountless authentication process may also be performed when theuser is remote so that the user can access network devices within thelogical network, using an access device, without having to enter networkdevice login credentials. While remote, the access device may access thenetwork devices in the local area network using an external network,such as a cloud network, the Internet, or the like. One or more gatewaysmay provide the network devices and/or access device connected to thelocal area network with access to the external network. To allowaccountless authentication, a cloud network server may provide a networkID and/or one or more keys to a network device and/or to the accessdevice (e.g., running an application, program, or the like). In somecases, a unique key may be generated for the network device and aseparate unique key may be generated for the access device. The keys maybe specifically encrypted with unique information identifiable only tothe network device and the access device. The network device and theaccess device may be authenticated using the network ID and/or eachdevice's corresponding key each time the network device or access deviceattempts to access the cloud network server.

In some embodiments, a home local area network may include a singlegateway, such as a router. A network device within the local areanetwork may pair with or connect to the gateway and may obtaincredentials from the gateway. For example, when the network device ispowered on, a list of gateways that are detected by the network devicemay be displayed on an access device (e.g., via an application, program,or the like installed on and executed by the access device). In thisexample, only the single gateway is included in the home local areanetwork (e.g., any other displayed gateways may be part of other localarea networks). In some embodiments, only the single gateway may bedisplayed (e.g., when only the single gateway is detected by the networkdevice). A user may select the single gateway as the gateway with whichthe network device is to pair and may enter login information foraccessing the gateway. The login information may be the same informationthat was originally set up for accessing the gateway. The access devicemay send the login information to the network device and the networkdevice may use the login information to pair with the gateway. Thenetwork device may then obtain the credentials from the gateway. Thecredentials may include a service set identification (SSID) of the homelocal area network, a media access control (MAC) address of the gateway,and/or the like. The network device may transmit the credentials to aserver, such as a cloud network server. In some embodiments, the networkdevice may also send to the server information relating to the networkdevice (e.g., MAC address, serial number, or the like) and/orinformation relating to the access device (e.g., MAC address, serialnumber, application unique identifier, or the like).

The cloud network server may register the gateway as a logical networkand may assign the first logical network a network identifier (ID). Thecloud network server may further generate a set of security keys, whichmay include one or more security keys. For example, the server maygenerate a unique key for the network device and a separate unique keyfor the access device. The server may associate the network device andthe access device with the logical network by storing the network ID andthe set of security keys in a record or profile. The cloud networkserver may then transmit the network ID and the set of security keys tothe network device. The network device may store the network ID and itsunique security key. The network device may also send the network ID andthe access device's unique security key to the access device. Thenetwork device and the access device may then communicate with the cloudserver using the network ID and the unique key generated for eachdevice. Accordingly, the user may remotely access the network device viathe cloud network without logging in each time access is requested.Also, the network device can communicate with the server regarding thelogical network.

In some embodiments, a local area network may include multiple gateways(e.g., a router and a range extender) and multiple network devices. Forexample, a local area network may include a first gateway paired with afirst network device, and a second gateway paired with a second networkdevice. In the event credentials for each gateway are used to create alogical network, a server (e.g., a cloud network server) may registerthe first gateway as a first logical network and may register the secondgateway as a second logical network. The server may generate a firstnetwork ID and a first set of security keys for the first logicalnetwork. The first set of security keys may include a unique securitykey for the first network device and a unique security key for theaccess device for use in accessing the first network device on the firstlogical network. The server may register the second gateway as thesecond logical network due to differences in the credentials between thefirst gateway and second gateway. The server may assign the secondgateway a second network ID and may generate a second set of securitykeys. For example, the server may generate a unique security key for thesecond network device and may generate a unique security key for theaccess device for use in accessing the second network device on thesecond logical network. The server may associate the first networkdevice and the access device with the first logical network by storingthe first network ID and the first set of security keys in a firstrecord or profile. The server may also associate the second networkdevice and the access device with the second logical network by storingthe second network ID and the second set of security keys in a record orprofile. The server may then transmit the first network ID and the firstset of security keys to the first network device, and may transmit thesecond network ID and the second set of security keys to the secondnetwork device. The two network devices may store the respective networkID and set of security keys of the gateway with which each networkdevice is connected. Each network device may send the respective networkID and the access device's unique security key to the access device. Thenetwork devices and the access device may then communicate with thecloud server using the respective network ID and the unique keygenerated for each device.

Accordingly, when multiple gateways are included in the home local areanetwork, multiple logical networks associated with different networkidentifiers may be generated for the local area network. When the accessdevice is located within range of both gateways in the local areanetwork, there is no problem accessing both network devices due to theability of the access device to perform local discovery techniques(e.g., universal plug and play (UPnP)). However, when the user islocated remotely from the local area network, the access device may onlybe associated with one logical network at a time, which prevents theaccess device from accessing network devices of other logical networkswithin the local area network.

FIG. 1 illustrates an example of a local area network 100. The localarea network 100 includes network device 102, network device 104, andnetwork device 106. In some embodiments, any of the network devices 102,104, 106 may include an Internet of Things (IoT) device. As used herein,an IoT device is a device that includes sensing and/or controlfunctionality as well as a WiFi™ transceiver radio or interface, aBluetooth™ transceiver radio or interface, a Zigbee™ transceiver radioor interface, an Ultra-Wideband (UWB) transceiver radio or interface, aWiFi-Direct transceiver radio or interface, a Bluetooth™ Low Energy(BLE) transceiver radio or interface, and/or any other wireless networktransceiver radio or interface that allows the IoT device to communicatewith a wide area network and with one or more other devices. In someembodiments, an IoT device does not include a cellular networktransceiver radio or interface, and thus may not be configured todirectly communicate with a cellular network. In some embodiments, anIoT device may include a cellular transceiver radio, and may beconfigured to communicate with a cellular network using the cellularnetwork transceiver radio. The network devices 102, 104, 106, as IoTdevices or other devices, may include home automation network devicesthat allow a user to access, control, and/or configure various homeappliances located within the user's home (e.g., a television, radio,light, fan, humidifier, sensor, microwave, iron, and/or the like), oroutside of the user's home (e.g., exterior motion sensors, exteriorlighting, garage door openers, sprinkler systems, or the like). Forexample, network device 102 may include a home automation switch thatmay be coupled with a home appliance. In some embodiments, networkdevices 102, 104, 106 may be used in other environments, such as abusiness, a school, an establishment, a park, or any place that cansupport the local area network 100 to enable communication with networkdevices 102, 104, 106. For example, a network device can allow a user toaccess, control, and/or configure devices, such as office-relateddevices (e.g., copy machine, printer, fax machine, or the like), audioand/or video related devices (e.g., a receiver, a speaker, a projector,a DVD player, a television, or the like), media-playback devices (e.g.,a compact disc player, a CD player, or the like), computing devices(e.g., a home computer, a laptop computer, a tablet, a personal digitalassistant (PDA), a computing device, a wearable device, or the like),lighting devices (e.g., a lamp, recessed lighting, or the like), devicesassociated with a security system, devices associated with an alarmsystem, devices that can be operated in an automobile (e.g., radiodevices, navigation devices), and/or the like.

A user may communicate with the network devices 102, 104, 106 using anaccess device 108. The access device 108 may include anyhuman-to-machine interface with network connection capability thatallows access to a network. For example, the access device 108 mayinclude a stand-alone interface (e.g., a cellular telephone, asmartphone, a home computer, a laptop computer, a tablet, a personaldigital assistant (PDA), a computing device, a wearable device such as asmart watch, a wall panel, a keypad, or the like), an interface that isbuilt into an appliance or other device e.g., a television, arefrigerator, a security system, a game console, a browser, or thelike), a speech or gesture interface (e.g., a Kinect™ sensor, aWiimote™, or the like), an IoT device interface (e.g., an Internetenabled device such as a wall switch, a control interface, or the like),or the like. In some embodiments, the access device 108 may include acellular or other broadband network transceiver radio or interface, andmay be configured to communicate with a cellular or other broadbandnetwork using the cellular or broadband network transceiver radio. Insome embodiments, the access device 108 may not include a cellularnetwork transceiver radio or interface. While only a single accessdevice 108 is shown in FIG. 1, one of ordinary skill in the art willappreciate that multiple access devices may communicate with the networkdevices 102, 104, 106. The user may interact with the network devices102, 104, or 106 using an application, a web browser, a proprietaryprogram, or any other program executed and operated by the access device108. In some embodiments, the access device 108 may communicate directlywith the network devices 102, 104, 106 (e.g., communication signal 116).For example, the access device 108 may communicate directly with networkdevice 102, 104, 106 using Zigbee™ signals, Bluetooth™ signals, WiFi™signals, infrared (IR) signals, UWB signals, WiFi-Direct signals, BLEsignals, sound frequency signals, or the like. In some embodiments, theaccess device 108 may communicate with the network devices 102, 104, 106via the gateways 110, 112 (e.g., communication signal 118) and/or thecloud network 114 (e.g., communication signal 120).

The local area network 100 may include a wireless network, a wirednetwork, or a combination of a wired and wireless network. A wirelessnetwork may include any wireless interface or combination of wirelessinterfaces (e.g., Zigbee™, Bluetooth™, WiFi™, IR, UWB, WiFi-Direct, BLE,cellular, Long-Term Evolution (LTE), WiMax™, or the like). A wirednetwork may include any wired interface (e.g., fiber, ethernet,powerline ethernet, ethernet over coaxial cable, digital signal line(DSL), or the like). The wired and/or wireless networks may beimplemented using various routers, access points, bridges, gateways, orthe like, to connect devices in the local area network 100. For example,the local area network may include gateway 110 and gateway 112. Gateway110 or 112 can provide communication capabilities to network devices102, 104, 106 and/or access device 108 via radio signals in order toprovide communication, location, and/or other services to the devices.The gateway 110 is directly connected to the external network 114 andmay provide other gateways and devices in the local area network withaccess to the external network 114. The gateway 110 may be designated asa primary gateway. While two gateways 110 and 112 are shown in FIG. 1,one of ordinary skill in the art will appreciate that any number ofgateways may be present within the local area network 100.

The network access provided by gateway 110 and gateway 112 may be of anytype of network familiar to those skilled in the art that can supportdata communications using any of a variety of commercially-availableprotocols. For example, gateways 110, 112 may provide wirelesscommunication capabilities for the local area network 100 usingparticular communications protocols, such as WiFi™ (e.g., IEEE 802.11family standards, or other wireless communication technologies, or anycombination thereof). Using the communications protocol(s), the gateways110, 112 may provide radio frequencies on which wireless enabled devicesin the local area network 100 can communicate. A gateway may also bereferred to as a base station, an access point, Node B, Evolved Node B(eNodeB), access point base station, a Femtocell, home base station,home Node B, home eNodeB, or the like.

The gateways 110, 112 may include a router, a modem, a range extendingdevice, and/or any other device that provides network access among oneor more computing devices and/or external networks. For example, gateway110 may include a router or access point, and gateway 112 may include arange extending device. Examples of range extending devices may includea wireless range extender, a wireless repeater, or the like.

A router gateway may include access point and router functionality, andmay further include an Ethernet switch and/or a modem. For example, arouter gateway may receive and forward data packets among differentnetworks. When a data packet is received, the router gateway may readidentification information (e.g., a media access control (MAC) address)in the packet to determine the intended destination for the packet. Therouter gateway may then access information in a routing table or routingpolicy, and may direct the packet to the next network or device in thetransmission path of the packet. The data packet may be forwarded fromone gateway to another through the computer networks until the packet isreceived at the intended destination.

A range extending gateway may be used to improve signal range andstrength within a local area network. The range extending gateway mayreceive an existing signal from a router gateway or other gateway andmay rebroadcast the signal to create an additional logical network. Forexample, a range extending gateway may extend the network coverage ofthe router gateway when two or more devices on the local area networkneed to be connected with one another, but the distance between one ofthe devices and the router gateway is too far for a connection to beestablished using the resources from the router gateway. As a result,devices outside of the coverage area of the router gateway may be ableto connect through the repeated network provided by the range extendinggateway. The router gateway and range extending gateway may exchangeinformation about destination addresses using a dynamic routingprotocol.

The gateways 110 and 112 may also provide the access device 108 and thenetwork devices 102, 104, 106 with access to one or more externalnetworks, such as the cloud network 114, the Internet, and/or other widearea networks. The cloud network 114 may include a cloud infrastructuresystem that provides cloud services. In certain embodiments, servicesprovided by the cloud network 114 may include a host of services thatare made available to users of the cloud infrastructure system ondemand, such as registration and access control of network devices 102,104, 106. Services provided by the cloud infrastructure system candynamically scale to meet the needs of its users. The cloud network 114may comprise one or more computers, servers, and/or systems. In someembodiments, the computers, servers, and/or systems that make up thecloud network 114 are different from the user's own on-premisescomputers, servers, and/or systems. For example, the cloud network 114may host an application, and a user may, via a communication networksuch as the Internet, on demand, order and use the application.

In some embodiments, the cloud network 114 may host a Network AddressTranslation (NAT) Traversal application in order to establish a secureconnection between the cloud network 114 and one or more of the networkdevices 102, 104, 106. For example, a separate secure TransmissionControl Protocol (TCP) connection may be established by each networkdevice 102, 104, 106 for communicating between each network device 102,104, 106 and the cloud network 114. In some embodiments, each secureconnection may be kept open for an indefinite period of time so that thecloud network 114 can initiate communications with each respectivenetwork device 102, 104, or 106 at any time. In some cases, other typesof communications between the cloud network 114 and the network devices102, 104, 106 and/or the access device 108 may be supported using othertypes of communication protocols, such as a Hypertext Transfer Protocol(HTTP) protocol, a Hypertext Transfer Protocol Secure (HTTPS) protocol,or the like. In some embodiments, communications initiated by the cloudnetwork 114 may be conducted over the TCP connection, and communicationsinitiated by a network device may be conducted over a HTTP or HTTPSconnection. In certain embodiments, the cloud network 114 may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner.

It should be appreciated that the local area network 100 may have othercomponents than those depicted. Further, the embodiment shown in thefigure is only one example of a local area network that may incorporatean embodiment of the invention. In some other embodiments, local areanetwork 100 may have more or fewer components than shown in the figure,may combine two or more components, or may have a differentconfiguration or arrangement of components.

Upon being powered on or reset, the network devices 102, 104, 106 may beregistered with the cloud network 114 and associated with a logicalnetwork within the local area network 100. FIG. 2 illustrates an exampleof a process 200 for registering one or more network devices, such asthe network devices 102, 104, 106 illustrated in FIG. 1. When multiplenetwork devices 102, 104, 106 and gateways 110, 112 are included withina local area network, the network devices and/or gateways may beinstalled at different times, resulting in the techniques described withrespect to FIG. 2 possibly occurring for each network device and/orgateway at different points in time. For example, a user may installnetwork device 102 at a first point in time on a first floor of theuser's house. Gateway 110 may also be located on the first floor,resulting in the network device 102 pairing with gateway 110. The usermay later install gateway 112 and network device 106 on a second floorof the user's home, resulting in the network device 106 pairing withgateway 112.

At 202, a network device may detect one or more gateways upon beingpowered on or reset. In some embodiments, a provisioning process mayoccur when the network device is powered on or reset and detected by anaccess device (e.g., access device 108). During the provisioningprocess, the access device may directly communicate with the networkdevice. In some embodiments, direct communication between networkdevices (e.g., network devices 102, 104, 106) and access device (e.g.,access device 108) may occur using various communications protocols,such as Universal Plug and Play (UPnP), Bluetooth®, Zigbee®,Ultra-Wideband (UWB), WiFi-Direct, WiFi, Bluetooth® Low Energy (BLE),sound frequencies, and/or the like.

The provisioning process may include pairing the network device with agateway and registering the gateway, network device, and access devicewith a server, such as a server located within the cloud network 114.For example, upon being powered on or reset to factory settings, thenetwork device may send or broadcast identification information to oneor more access devices. The identification information may be sentduring a discovery process. For example, the identification informationmay be sent in response to a discovery request from an access device. Insome cases, the identification information may include a name of thenetwork device.

An application, program, or the like that is installed on and executedby the access device may receive the identification information from thenetwork device. When the application on the access device is launched bya user, the access device may display the identification information forselection by the user. Once the network device identificationinformation is selected, the access device may send a signal to thenetwork device indicating that it has been selected. The network devicemay then send to the access device a list of gateways that are detectedby the network device. The access device may receive and display thelist of gateways. In some embodiments, the list of gateways includesmultiple gateways (e.g., gateways 110 and 112) that are located withinthe local area network. The user may select the gateway that the userwishes for the network device to pair. For example, the gateway thatprovides the best signal strength for the network device may beselected. The access device may then prompt the user to enter logininformation that is required for accessing the network signals providedby the selected gateway. For example, the login information may be thesame information that was originally set up to access the gatewaynetwork signals (e.g., when the gateway was initially installed). Onceentered, the access device may send the login information to the networkdevice. The network device may use the login information to pair withthe selected gateway. As one example, network device 102 and networkdevice 104 may be paired with gateway 110, and network device 106 may bepaired with gateway 112.

Once paired with a gateway, the network device may be registered with acloud network (e.g., cloud network 114). For example, the access device(e.g., via the application, program, or the like) may instruct thenetwork device to register with the cloud network upon receivingconfirmation from the network device that it has been successfullypaired with a gateway. At 204, the network device may obtain credentialsfrom the gateway as part of the registration process. For example,network device 102 may obtain credentials from gateway 110. At a same orlater point in time, network devices 104 and 106 may obtain credentialsfrom gateways 110 and 112, respectively. In some embodiments, thecredentials may include a SSID of the local area network and a MACaddress of the gateway. An SSID received from two gateways (e.g.,gateways 110, 112) may be the same due to the gateways both being withinthe same local area network. In some cases, the SSID of the two gatewaysmay be different. The MAC address of each of the gateways may be uniqueto each gateway. As a result of each gateway having a unique MACaddress, the credentials obtained from a gateway may be unique to thatparticular gateway. One of ordinary skill in the art will appreciatethat other credentials may be obtained from a gateway, such as anInternet Protocol address, or the like.

The network device may then send the gateway credentials to the cloudnetwork at 206. For example, the network devices 102, 104, 106 may sendcredentials for the gateway with which each is paired to the serverlocated within the cloud network 114. For example, network device 102may transmit the credentials obtained from gateway 110 to the server,and network device 106 may transmit the credentials obtained fromgateway 112 to the server. In some embodiments, the network device mayalso send information relating to the network device (e.g., MAC address,serial number, make, model number, firmware version, and/or an interfacemodule identifier, or the like) to the server, and/or informationrelating to the access device (e.g., MAC address, serial number,application unique identifier, or the like) to the server. In someembodiments, the communication of the credentials, the network deviceinformation, and/or the access device information sent from the networkdevice to the cloud network server may be in a Hypertext TransferProtocol (HTTP) format, a Hypertext Transfer Protocol Secure (HTTPS)format, a secure Transmission Control Protocol (TCP) format, or thelike. One of ordinary skill in the art will appreciate that othercommunication formats may be used to communicate between the networkdevice and the cloud network server.

Once the credentials, network device information, and/or access deviceinformation are received by the server, the server may register eachgateway as a logical network within the local area network and maygenerate a network ID for each logical network. For example, the servermay register the gateway 110 as a first logical network. During theregistration process, the server may generate a first network ID foridentifying the first logical network. As noted above, one of ordinaryskill in the art will appreciate that any number of gateways may bepresent within the local area network, and thus that any number oflogical networks may be registered for the local area network. Theserver may further generate a first set of security keys forauthenticating the network device and the access device. For example,the server may generate a unique key for the network device 102 and aseparate unique key for the access device 108.

In some embodiments, as previously described, network device 104 mayalso be paired with gateway 110 at the same or a later point in time asthe network device 102. During registration of the network device 104,the server may determine that the access device 108 has already beenregistered with another network device (e.g., network device 102) thatis associated with the same logical network of gateway 110. In suchembodiments, the server may retrieve the first network ID that was usedin registering the first logical network. The server may also generate anew unique security key for the network device 104, and may retrieve theunique key that was previously generated for the access device 108 whenregistering the gateway 110 as the first logical network.

The gateway 112 may also be registered by the server as a second logicalnetwork with a second network ID. A second set of security keys may begenerated for the network device 106 and the access device 108. Forexample, the server may generate a unique security key for the networkdevice 106 and a unique security key for the access device 108 as itrelates to the second logical network. In some embodiments, the gatewaymay 112 be installed at a later point in time after the gateway 110 isinstalled, and thus may be registered as the second logical network atthe later point in time.

A record or profile may then be created for associating each network IDwith the credentials of a corresponding gateway, the correspondingnetwork device(s), and the access device. For example, the server of thecloud network 114 may associate the first network ID with thecredentials of gateway 110. Similarly, the server may associate thesecond network ID with the credentials of gateway 112. In someembodiments, the server performs the association by generating andstoring a record including the network ID, the set of security keys, thegateway credentials, the network devices associated with the network ID(e.g., MAC address or serial number of a network device), the accessdevices associated with the network ID (e.g., MAC address, serialnumber, application unique identifier, or the like), and/or any otherinformation relevant to the network devices and/or gateways. Forexample, the server may store the first network ID and the first set ofsecurity keys in a first record at a first memory space (e.g., in Flash,DRAM, a database, or the like) along with the SSID and MAC address forgateway 110 and an identifier of the network devices 102 and/or 104. Theserver may also store the second network ID and the second set ofsecurity keys in a second record at a second memory space along with theSSID and MAC address for gateway 112 and an identifier of the networkdevice 106. In some embodiments, an example of a network deviceidentifier may include a MAC address of the network device, a serialnumber of the network device, or any other unique identifier.

Each of the first and second network IDs may include a unique number oralphanumeric string generated sequentially or randomly. For example, thefirst time a network device and an associated gateway are registered onthe cloud network 114, the unique network ID for the logical network ofthe gateway may start with 7000000. Each subsequent logical network thatis created may be a sequential increment of the initial network ID(e.g., 7000001, 7000002, 7000003, etc.). As another example, the networkID may be generated by a random or pseudo-random number generator. Oneof ordinary skill in the art will appreciate that other techniques forgenerating a unique ID may be used. The technique used to generate thenetwork IDs may be dependent on a type of database that is included inthe cloud network 114. For example, different databases may havedifferent proprietary mechanisms for creating a unique identifier.

The set of keys generated for each logical network may be generatedusing database specific technique. For example, a MySQL technique may beused to generate the sets of keys. Each key may include a universallyunique identifier (UUID) or a globally unique identifier (GUID). Asdescribed above, for each logical network, the server may generate aunique key for a network device and a separate unique key for an accessdevice.

At 208, the network device may receive the network ID and the set ofsecurity keys. For example, once the server has generated a record orprofile associating the network device 102 with the first logicalnetwork, the server may transmit the first network ID and the first setof security keys to the network device 102. The network device 102 maystore the first network ID and one or more keys of the first set ofkeys. For example, the network device 102 may store the unique securitykey that was created by the server for the network device 102.

As noted previously, the network devices 102, 104, 106 and gateways 110,112 may be installed at different times. For example, in someembodiments, network device 104 may be installed at a point in timeafter the first logical network is created based on the pairing betweengateway 110 and network device 102. In such embodiments, upon beingpowered on, the network device 104 may pair with gateway 110, obtaincredentials from gateway 110, and transmit the credentials to the serverin the cloud network 114 using similar techniques as those describedabove. The server may associate the network device 104 with thepreviously generated first network ID. As described above, the servermay also generate a new unique security key for the network device 104,and may retrieve the unique key that was previously generated for theaccess device 108 when registering the first logical network. Thenetwork device 104 may then receive and store the first network ID andthe security keys from the server.

At 210, the network device may send the network ID and the set ofsecurity keys to the access device. For example, the network device 102may send to the access device 108 the first network ID and the uniquesecurity key generated for the access device 108. The network device 102and the access device 108 may then communicate with the cloud networkserver using the first network ID and each device's unique key. In someembodiments, the network device and the access device may generate asignature using their respective security key. The signature is sent tothe cloud network server along with a communication from the networkdevice or access device. The cloud network server may process thesignature in order to authenticate each device, as described below. Thenetwork device and access device may use different techniques togenerate a signature.

A network device may generate a signature using its uniquely generatedsecurity key. For example, the signature may be expressed as:Authorization=MacAddress“:”Signature“:”ExpirationTime. The Authorizationterm may be an attribute, and the MacAddress, Signature, andExpirationTime terms may include values for the Authorization attribute.In particular, the MacAddress value may include the MAC address of thenetwork device, which may include a unique alphanumeric or numericstring. The network device may retrieve its MAC address from memory andplace it in the MacAddress field. The Signature value may be expressedas: Signature=Base64(HMAC-SHA1(PrivateKey, StringToSign)). The Signaturevalue may include an alphanumeric or numeric string. HMAC-SHA1 is anopen source technique that includes a Hash-based Message AuthenticationCode (HMAC) using a SHA1 hash function. The HMAC-SHA1 technique uses thevalues PrivateKey and StringToSign as inputs. The PrivateKey inputincludes the unique security key that was generated by the server forthe network device. The StringToSign input may be expressed asStringToSign=MacAddress+“\n”+SerialNumber+“\n”+ExpirationTime.Accordingly, the StringToSign input is generated by appending a serialnumber of the network device and an expiration time to the networkdevice's MAC address. The ExpirationTime term may indicate the period oftime for which the signature is valid. In some embodiments, theExpirationTime term may include a current time at which the signature isgenerated plus period of time for which the signature is valid. In oneexample, the ExpirationTime term may be expressed asExpirationTime=Number of seconds since Jan. 1, 1970.

The network device may place the signature in a data packet fortransmission with a communication signal to the cloud network server.The network device may also place the network ID in the data packet. Thesignature and the network ID, if included, may be used by the cloudnetwork server to verify that the network device is associated with thelogical network. In some embodiments, a signature is provided with eachcommunication sent from the network device to the server. Once thesignature is received by the server, the server generates a signatureusing the same expression as that used by the network device. Forexample, the server may retrieve the network device's key and otherrelevant information from storage and generate the signature using thekey and the other information using the expression described above. Theserver then verifies whether the signatures match. Upon determining thatthe signatures match, the server authenticates the network device'scommunication.

An access device may also generate a signature using its uniquelygenerated security key. For example, the access device signature may beexpressed as: Authorization=SDU UniqueId“:”Signature“:”ExpirationTime.The Authorization term may be an attribute, and the SDU UniqueId,Signature, and ExpirationTime terms may include values for theAuthorization attribute. The SDU UniqueId term may include a uniquephone identifier. The SDU UniqueId value may depend on the type ofaccess device that is used and the type of values that may be accessedand/or generated by the type of access device. In some cases, one typeof access device may not allow an application to access a uniqueidentifier of the access device (e.g., a serial number, UUID, or thelike). In such cases, the SDU UniqueId value may include a valuegenerated by an application or program installed on and executed on theaccess device that is used to access the network device. The value maybe unique to the application or program that generated the value. Inother cases, another type of access device may allow an application toaccess a unique identifier of the access device. In such cases, the SDUUniqueId value may include a value that is unique to the access deviceitself, such as a serial number, UUID, or the like. In this example, theaccess device may retrieve the unique value from storage within theaccess device. One of ordinary skill in the art will appreciate thatother unique identifiers may be used to uniquely identify the accessdevice. The Signature value may be expressed as:Signature=Base64(HMAC-SHA1(PrivateKey, StringToSign)). Using thisexpression, the input to the HMAC-SHA1 technique may include aPrivateKey term and a StringToSign term. The PrivateKey input includesthe unique security key that was generated by the server for the accessdevice with regard to a particular logical network. The StringToSigninput may be expressed as StringToSign=UniqueId+“\n”+“\n”+ExpirationTime. The StringToSign value is different from the StringToSign valuegenerated by network device in that no serial number is included.Accordingly, the StringToSign input is generated by appending anexpiration time to the access device's unique identifier. TheExpirationTime term may indicate the period of time for which thesignature is valid, similar to that above for the signature generated bythe network device.

The access device may place the signature in a data packet and maytransmit the data packet to the cloud network server with acommunication signal. The network device may also place the network IDin the data packet. The signature and the network ID, if included, maybe used by the cloud network server to verify that the access device isassociated with the logical network and authorized to communicate withone or more network devices associated with the logical network. In someembodiments, a signature is provided with each communication sent fromthe access device to the server. The cloud server may receive thesignature and may generate a signature using the same expression as thatused by the access device. For example, the server may retrieve theaccess device's key and other relevant information from storage andgenerate the signature using the key and the other information using theexpression described above. The server then verifies whether thesignatures match. Upon determining that the signatures match, the serverauthenticates the access device and allows it to communicate with one ormore of the network devices associated with logical network.

Once the provisioning process is completed, the access device 108 mayaccess the network device 102 locally via the gateway 110 (e.g.,communication signal 118) or remotely via the cloud network 114 (e.g.,communication signal 120). In some embodiments, the communicationbetween the access device 108 and the cloud network 114 may be a HTTP orHTTPS communication. One of ordinary skill in the art will appreciatethat other communication mechanisms may be used to communicate betweenthe access device 108 and the cloud network 114.

The network 100 may enable a user to monitor and/or control operation ofthe devices 102 and 104. For example, a user may monitor and/or controloperation of devices by interacting with a visual interface of thegateway 110 (i.e., a web page for gateway 110) and/or a visual interfacerendered on a display of an access device, such as access device 108. Insome embodiments, an application may be run on the access device. Theapplication may cause the access device to present a graphical interfacethat includes a visual interface for each device accessible on thenetwork 100.

A network device may generate and/or provide a “status” of the networkdevice. In certain embodiments, the status or state of a network devicecan be indicated on a visual interface on the access device, for examplewithin the tile with text and/or graphically. The status of the networkdevice can change based on time (e.g., a period, an interval, or othertime schedule). The status of a network device may be any piece ofinformation pertinent to that particular network device. The status of anetwork device may be any changeable variable of that particular networkdevice. For example, the status of a network device may include a stateof the-network device itself (e.g., on or off) or how the network deviceis situated within the network with respect to the other network andother network devices throughout the network. For example, the status ofa network device may refer to the network device's proximity to anothernetwork device and/or its ability to communicate with another networkdevice because of the relative signal strength between the two networkdevices. In certain embodiments, the status can include a value or someother information indicating a unit of measure for a setting or anattribute related to operation of a device connected to the networkdevice. The setting or the attribute can be adjustable within a range ofvalues. For example, the device connected to the network device can be alight bulb and the status can include a value corresponding tobrightness (e.g., a percentage of total brightness) emitted by the lightbulb when the light bulb is powered-on. In another example, the devicecan be a motion sensor and the status can include a value correspondingto sensitivity of the sensor in a range of values between 0 to 100 whenthe sensor is powered-on. In yet another example, the device can be afan and the status can include a value corresponding to a speed of thefan on a scale of 0 to 100 when the fan is powered-on.

As described above, upon being powered on or reset, the-network devices102 and/or 104 may be registered with the cloud network 114 andassociated with a logical network within the local area network 100.Similarly, upon being powered or switched off or otherwise beingdisconnected from the network 100, the status of the-network device 102would be known and stored by a cache (not shown) associated with thenetwork 100. For example, cloud network 114 may include storage (e.g.cache) that stores the status of the network devices within each localarea network 100 it is connected to and/or provides access to. Inanother example, the gateway 110 may include storage that stores thestatus of the network devices within each local area network it isconnected to and/or provides access to. More specifically, the statusstored in the cache may include a status table which indicates thecurrent status of each network device (as of its last communication witheach network device). A status table may include all statuses ofeach-network device, or individual storage tables for each local areanetwork or other subset of its network devices/networks. In oneembodiment, a change in status may prompt the-network device to push itschange in in status to the cloud network 114 for storage or updating ofthe cloud's stored status table. In another embodiment, cloud network114 and/or gateway 110 may continuously (or periodically) communicatewith each-network device to check to see if its status has changed.

In some embodiments, a network device (e.g. network device 102 and/or104) may, upon connecting to the local area network 100, check thestatus of the-network devices on the network 100. In other embodiments,one-network device may check the status of one or more of the othernetwork devices on the network 100. The network device may seek to checkthe status of another network device or access device for variousreasons, including to display such status(es) to a user on a display orotherwise, to check whether that network device belongs to the samenetwork, to synchronize or coordinate any scheduled executions, toupdate an attribute based on adjustment received among others. Forexample, a network device or user may desire to check various statuseson a connected device, such as power level, timestamped activity history(e.g. temperature for a thermostat, motion for a motion detector, etc.),how long it has been active/turned on, attributes for operation of theconnected device (e.g., a brightness of a lamp, a speed of a fan, or asensitivity of a sensor, etc.), among many others.

In some embodiments, a device, such as the access device 108 shown inFIG. 1 or the gateway 110, connected to the network 100 can communicatean updated status of a network device, such as the network devices 102and/or 104. The updated status can be communicated via the network 100and can include an adjustment that affects a status of the networkdevice. The adjustment can include an amount of change to one or moreattributes, one or more settings, or a combination thereof related tooperation of the network device connected to the network 100. The accessdevice 108 or the gateway 110 can present a graphical interface that canreceive input corresponding to an adjustment to a status of a device. Insome embodiments, the updated status of the network device communicatedto the network 100 can be received by a network device to which theupdated status applies, or can be received by the gateway 110, the cloudnetwork 110, or any other device in communication with the network. Ifthe device cannot directly receive the updated status, it can alsoreceive the updated status from the cloud network 114, the gateway 110,or the other devices in the network 100. In some embodiments, thenetwork device can communicate its updated status to the network 100,which can indicate whether the status has been updated. The updatedstatus can be received by the access device or any other device in thenetwork 100. In some embodiments where the access device is not locatedwithin the network 100, the access device may not immediately receivethe updated status. The updated status can be stored by the cloudnetwork 114 or the gateway 110 for communication to the access device.The status of the network device can indicate whether an adjustment wasmade based on an adjustment in a setting or an attribute transmitted bythe access device. Alternatively, or additionally, the access device canreceive, from any other network device connected to the network 100, astatus update indicating whether the adjustment was in fact made at anetwork device.

A network device seeking to check the status of any other device on thenetwork 100 may communicate with the cloud network 114, to which alldevices on the network 100 are connected either directly or indirectly.Since the cloud network 114 and/or the gateway 110 can store an updatedtable/list of the statuses of each of the network devices 102 and 104within the requesting network's local area network, the cloud network114 and/or gateway 110 may communicate such status data to the networkdevices 102 and 104 and the access device. For example, if-networkdevices 102 and 104 were to each turn on and communicate their statusesto cloud network 114, cloud network 114 may analyze the status ofnetwork devices 102 and 104 and communicate to-network devices 102 and104 that they are each connected to the same local area network 100.

FIG. 3 illustrates an example of a network 300, according to embodimentsof the present invention. Specifically, the network 300 can be awireless local area network enabling an access device to communicatewith network devices to control adjustment of attributes related tooperation of the network devices. Network 300 includes network device302, network device 304, network device 306, and network device 308. Thenetwork 300 also includes access device 108. In other words, the network300 may be substantially similar to the network 100 except that accessdevice 108 has been turned on near the network 300, to which it isassociated, or has entered an area to which the network 300 can reach.

When access device 108 can enter the network 300 as shown in FIG. 3,access device 108 may be authenticated based on the access device'sauthentication with the logical network or may otherwise commencecommunication with cloud network 114. Access device 108 may alsocommunicate notification of its presence or other information directlyto other network devices 302-308 within network 300, as shown in FIG. 3by communication paths 330. As noted, such communication may includevarious communications protocols, such as Universal Plug and Play(UPnP), Bluetooth®, Zigbee®, Ultra-Wideband (UWB), WiFi-Direct, WiFi,Bluetooth® Low Energy (BLE), sound frequencies, and/or the like. Forexample, access device 108 may communicate to all other devices innetwork 300, including network device 302, network device 304, networkdevice 306, and network device 308, information/data regarding itsstatus. Such status data may include the fact that it is present andturned on, or other status data/information. At any time that networkdevices 302, 304, 306 and 308 recognize that access device 108 ispresent at network 300, the network devices may communicate back toaccess device 108. For example, the network devices may send anacknowledgement (e.g., ACK signal) back to access device 108 to confirmthat they received the status data sent by access device 108. Thenetwork devices may also send their own status data to access device108.

While network devices 302-308 and access device 108 may each receivecommunication from other network devices around the network 300,including the status of each of those network devices, network devices302-308 and/or access device 108 may be continuously scanning network300 (including, for example, running discovery algorithms) to determinewhether any devices within the network have moved, turned on/off orotherwise added to or subtracted from the network 300, or have otherwisechanged statuses.

Since network devices 302-308 and access device 108 may each receivecommunication from other devices around network 300, including thestatus of each of those devices, each network device within network 300may know the status of each other network device in the network 300. Forexample, access device 108 or devices 302-308 may not be required tocommunicate with cloud network 114 in order to obtain one or more ofsuch statuses. Since cloud network 114 is an external network and may beremote from network 300, communication between network devices withinthe network 300 and cloud 114 may take more time than communicationbetween two devices within network 300. For example, communicationbetween devices within network 300 may take anywhere from 1 millisecondto 100 milliseconds, while communication between a device within network300 and the cloud network 114 may take anywhere from 50 milliseconds to1 second or more). Furthermore, if a network device is retrievinginformation from cloud 114, the request must travel from the networkdevice to cloud network 114, and then the information must travel backfrom cloud network 114 to the network device. This process may doublethe latency caused by retrieving information with cloud 114. Therefore,devices within the network 300 may choose to send and receive/retrievestatuses directly with other devices within the network 300 instead ofcommunicating such information via cloud network 114. When a networkdevice receives status data from another network device on the device'slocal area network 300, it may store that status data so that it mayretrieve and use that status data at a later time.

FIG. 4 illustrates an example of a network 400, according to embodimentsof the present invention. The local area network 400 may include networkdevice 302, network device 304, network device 306, network device 308,and access device 108. FIG. 4 also illustrates that one or more networkdevices 302-308 and/or access device 108 may include a storage device,such as a cache, for storing data, including data regarding its ownstatus and data regarding statuses received from the other deviceswithin local area network 400. For example, access device 108 may, afterbeing powered up, broadcast/send its status to network device 308 viacommunication 434. Network device 308 may store the status data receivedfrom access device 108 until the next time access device 108 updates itsstatus by sending new/updated status data to network device 308. Cachemay be used for storage within network devices 302-308 and/or accessdevices within the local area network 400 so that each of the devicesmay be able to quickly retrieve the data it needs from storage. Anapplication operating on the access device 108 can access the cache toobtain information to display the visual interface for each networkdevice 302-308 registered within the network 400. Although a cachingdevice may be used to store such data within the network and/or accessdevices within the local area network 400, other types of storage may beused.

The cache can contain a known interface list including interfaceinformation for different, known types of devices. The known list caninclude a record for each network device known by the access device 108to exist on the network 400. When an application is run on the accessdevice 108, the access device 108 can access the known interfaces in thecache to present the display of access device 108. The display canpresent one or more visual interfaces, each corresponding to a networkdevice known to exist on the network 400. Each visual interface can begenerated based on a visual interface module corresponding to eachdevice on the network 400. In an example, the display can include avisual interface (e.g., a module tile) for each device in the network400 having an interface in the known interface list.

The cache can also contain known status information about each networkdevice in the known device list. When the application is run on theaccess device 108, the access device 108 can access the known statusinformation in the cache to present a status display. The access device108 can populate each tile with an indicator representing the respectiveknown status information for each device in the known device list. Thestatus display can include an indicator of one or more attributes, oneor more settings, or a combination thereof related to operation of eachdevice in the network 400. For example, the status display can include aspeed of a fan (e.g., a fan speed of 56 in a range of values between 0and 100) of the network device 302 (e.g., a fan), a value of sensitivityof a sensor (e.g., a value of 34 in a range of values 0-100) for thenetwork device 304 (e.g., a motion sensor), a value of brightness (e.g.,65 percent brightness) for the network device 306 (e.g., a light bulb),and a value of temperature (e.g. a slow cooker). Although shown ashaving a single indicator for an attribute or a setting related tooperation of a network device, the status display can present aplurality of indicators corresponding to different attributes and/orsettings related to operation of a network device.

In some embodiments, the cache can include other information about anetwork device. The other information can indicate a device's firmwareversion, last known firmware update status, connectivity to cloudstatus, registration status (e.g., whether the network device has a keyor not), and other such information. The cache can include informationthat could be used for troubleshooting. In embodiments described below,the access device 108 can access status information from another otherdevice on the network 400 and can use that information to update its owncache, update the status display, and/or pass the information to thecloud network 114 and/or the gateway 110 for trouble shooting and/orstorage.

Even though each network device may know and store (e.g. in cache) thestate of each other network device within local area network 400, anetwork device may not know when another network device changes status(e.g. turns/powers off). However, network devices and/or access deviceswithin local area network 400 may broadcast/send any updates in itsstatus to other devices on the network. For example, if network device302 changes status, it may send status data to the other networkdevices, such as network devices 304, 306 and 308 and to access device108. However, network device 302 may not know which devices to updatesince the other devices may change statuses periodically (e.g. turnoff).

Therefore, a network or access device may subscribe to another networkor access device within local area network 400. For example, networkdevices 304, 306 and 308 and access device 108 may subscribe to statusdata notifications/updates from network device 302. Such a subscriptionmay be registered for upon initial connection with network device 302when network device 302 first enters local area network 400 or at anyother time after network device 302 has been associated with local areanetwork 400. Subscriptions may be controlled to last indefinitely or mayexpire after a certain predetermined period of time after initialsubscription. However, network devices may re-subscribe to anothernetwork device before or after their previous subscription has expired.

Subscriptions between network device and/or access devices may beregistered, similar to registering a network device upon initialentrance into the local area network, including security registrationsdescribed herein with respect to FIGS. 1 and 2. For example, a networkdevice may send its unique security key, which it may have stored alongwith its network ID after being registered on the network, to a networkdevice to which it wants to subscribe. However, subscriptions may takeon many other forms, including sending a different form ofidentification to a network device to which a network device wants tosubscribe. However, subscriptions may take on many other forms,including sending a different form of identification to a network deviceto which a network device wants to subscribe.

Upon receiving a subscription from another network device or accessdevice, the device being subscribed to may store a list of the devicesthat subscribed to it. For example, network device 302 may store a listof network devices 304, 306 and 308 and access device 108 after thosedevices subscribe to network device 302. Then, when network device 302undergoes a change in status, network device 302 may send that change instatus to only the devices that had previously subscribed to it butwhere the subscription had not yet expired. Furthermore, according tosome embodiments, the subscription list of a network device may beautomatically updated if that device receives notification that anotherdevice has left the range of the local area network, either from thatdevice itself or from a different device. Therefore, the various deviceswithin a given local area network, such as network 400, each containcontinuously updated statuses of each other device on the network andobtain those statuses and updates through direct communication withoutnecessary use of the cloud.

FIG. 5 illustrates an access device 108 that is located remotely fromnetwork 500 (e.g. local area network), according to embodiments of thepresent invention. Local area network 500 includes gateway 110 andnetwork devices 502 and 504 (which may be, for example, the same as anyof network devices 302-308 in FIGS. 3 and 4), as shown in FIG. 5.However, network 500 may also include a variety of other network devicesand one or more access devices directly connected to network 500.Gateway 110 is connected to cloud network 114, and allows networkdevices 502 and 504 to connect to cloud 114, the internet, or otherexternal networks via gateway 110. In some embodiments, the networkdevices 502 and 504 may include home automation devices that allow auser to access, control, and/or configure various home applianceslocated within the user's home, such as a television, radio, light,microwave, iron, and/or the like.

Access device 108 is not directly connected to network 500. Instead,access device 108 is external to network 500 and may connect to cloudnetwork 114 and to network 500 via cloud network 114. As noted, networkdevices 502 and 504 may change status on a periodic basis. In someembodiments, even when external to and not directly connected to network500, an access device may request to check the status of the devices onthe network. When access device 108 seeks to check the status of anydevice on the network, the access device 108 may transmit/send acommunication 536 to the cloud network 114, to which all devices on thenetwork are connected either directly or indirectly via gateway 110.Since the cloud network 114 stores an updated table/list of the statusesof each of the devices within the requesting access device's network,the cloud network 114 may transmit a communication 538 of such statusdata to the access device 108. For example, after network devices 502and 504 are turned on, authenticated and are a part of network 500,network devices 502 and 504 may communicate their statuses to cloudnetwork 114. Furthermore, any time the status of network devices 502 and504 changes, the device that incurred a status change may push/sendinformation (e.g. an indication) of that status change to cloud network114. Cloud network 114 may store, in cache 526 or otherwise, thestatuses (which may be time stamped in metadata or otherwise) of networkdevices 502 and 504. Therefore, when access device 108 requests fromcloud network 114 the statuses of devices on network 500, cloud 114 maysend its most recently stored/updated statuses to access device 108.

To obtain the most updated status data of devices within network 500,cloud 114 may, upon receiving a request for status data related tonetwork devices 502 and 504, transmit/send a communication 532 (e.g.request, query, etc.) for such status data to network devices 502 and504 via gateway 110. Once network devices 502 and 504 receive thisrequest, network devices 502 and 504 may send a communication 534 (e.g.updated status data) to cloud 114 to replace the previouslystored/cached statuses in cache 526. Upon receipt of updated status data534 from network 500, cloud 114 may send a communication 538 of suchstatus data to the access device 108.

However, the process of cloud network 114 requesting updated statusesfrom network devices 502 and 504 within network 500 may cause latencywithin the system. More specifically, the time required for cloudnetwork 114 to request updated statuses from network devices 502 and 504and to in turn receive updated statuses from network devices 502 and 504may be substantially greater than the time required for cloud network114 to send its currently stored statuses (without being updated) fornetwork devices 502 and 504 to access device 108. For example, of thetotal time required for access device 108 to receive updated statusesfrom cloud network 114, 80% or more of that total time may include cloudnetwork 114 requesting updated statuses from network devices 502 and504. On the other hand, of the total time required for access device 108to receive updated statuses from cloud network 114, 20% or more of thattotal time may include the status data being transmitted from cloudnetwork 114 to access device 108. Since a majority of the processrequired for access device 108 to request and receive status data fornetwork devices 502 and 504 is the transmission of data between cloud114 and network devices 502 and 504, the access device 108 and cloudnetwork 114 may maximize efficiency by minimizing the effect of thetransmission of data between cloud 114 and network devices 502 and 504on the whole process/system.

Techniques and systems are described herein for setup of multiple IoTnetwork devices. Specifically, various techniques and systems areprovided for setup of multiple similar (or, in other embodiments,disparate) IoT devices at substantially the same time using jointauthentication. For example, multiple new network devices may generatesetup access points at substantially the same time and attempt to join alocal area network. A device on the network may detect communicationsfrom the new devices including a request to join the network and/oridentification information. The device may then connect to the newnetwork devices in various different ways to receive such identifyinginformation, and may authenticate the network devices at substantiallythe same time before allowing the new devices to join the network. Theexisting network device may also use other existing network devices ormay use communication between new network devices to facilitate theprocess of authenticating and joining the new network devices on to thenetwork. Exemplary embodiments of the present invention are describedherein.

FIG. 6 illustrates an example of a local area network 600 including agateway and three network devices, according to embodiments of thepresent invention. The local area network 600 includes network devices302, 304 and 306. However, network 600 may include more or less networkdevices at any given time. Also included in FIG. 6 is new networkdevices 608, 610 and 612.

New network device 608 is connected to (or includes) setup access point609, new network device 610 is connected to (or includes) setup accesspoint 611, and new network device 612 is connected to (or includes)setup access point 613. A setup access point (e.g. wireless accesspoint), such as setup access points 609, 611 and 613, allows wirelessdevices to connect to a network using WiFi, Zigbee, near fieldcommunication, or other standards. Identification information may besent from one of the new network devices to gateway 110 via the networkdevice's setup access point. The identification information may also besent as an automatic component of being powered on for the first time orreset of the new network device. In some cases, the identificationinformation may include a name of the network device or otherinformation identifying the network device. The identification may besent directly to the gateway, may be sent to the gateway via anothergateway or network device, may be sent to the gateway via a cloudnetwork connected to both the network device and the gateway, amongother methods of communication.

New network devices 608, 610 and 612 may be turned/powered on at thesame time or at substantially the same time. For example, new networkdevices 608, 610 and 612 may be powered on within 30 seconds, 1 minute,2 minutes, 5 minutes, etc. of each other. After one or more of the newnetwork devices are turned on near local area network 600, networkdevices 608, 610 and 612 may transmit a notification or other indicationof their presence. The notifications may include identificationinformation or other information identifying the network device that hasbeen powered on. The notifications may also include a request to jointhe network. Alternatively, new network devices 608, 610 and 612 maysend a separate communication including a request to join the network.

The notifications/indications sent from the new network devices may bein the form of beacons containing various information, includingidentification information of the device, identification information ofthe network, a timestamp, information indicating networkbandwidth/latency or other capability information, among otherinformation. Furthermore, beacon frames may be transmitted periodicallyto announce the presence of the network device.

Because network devices 608, 610 and 612 may be powered on atsubstantially the same time or within seconds or minutes of each other,a device that is already on the network, such as one or more of networkdevice 302, network device 304, and network device 306, may receive thenotifications/beacons from the new network devices 608, 610 and 612,including requests from the new network devices 608, 610 and 612 to jointhe network, at substantially the same time. Subsequently, one or moreof network devices 302, 304 and 306 may connect to new network devices608, 610 and 612. For example, one or more of network devices 302, 304and 306 may generate a communication connection/path with one or more ofnew network devices 608, 610 and 612. Furthermore, before allowing newnetwork devices 608, 610 and 612 to communicate with gateway 110 and/ornetwork devices already on the network, the network or a device on thenetwork may authenticate new network devices 608, 610 and 612 to confirmthat the new network devices are allowed/desired to join the network.Example authentication methods are described herein with respect toFIGS. 1 and 2.

Gateway 110 may facilitate the process of connecting the new networkdevices 608, 610 and 612 to the network. For example, as shown in FIG.7, the network 700 may not include network devices already connected tothe network, such as network devices 302, 304 and 306 as shown in FIG.6. New network devices 608, 610 and 612 may be turned/powered on at thesame time or at substantially the same time. After one or more of thenew network devices are turned on near local area network 600, networkdevices 608, 610 and 612 may transmit a notification or other indicationof their presence. The notifications may include identificationinformation or other information identifying the network device that hasbeen powered on. Gateway 110 may receive the notifications/beacons fromthe new network devices 608, 610 and 612, including requests from thenew network devices 608, 610 and 612 to join the network. Gateway 110,similar to the network devices 302, 304 and/or 306 in FIG. 6, mayreceive such notifications/requests from the new network devices atsubstantially the same time. Subsequently, gateway 110 may connect tonew network devices 608, 610 and 612, as shown for example in FIG. 12.For example, gateway 110 may generate a communication connection/pathwith one or more of new network devices 608, 610 and 612. Furthermore,before allowing new network devices 608, 610 and 612 to communicate withgateway 110 and/or network devices already on the network, the networkor a device on the network may authenticate new network devices 608, 610and 612 to confirm that the new network devices are allowed/desired tojoin the network.

FIG. 8 illustrates an example of a local area network 800 including agateway and a network device connected to three new network devices,according to embodiments of the present invention. As noted, networkdevices 608, 610 and 612 may generate setup access points that anexisting network device (e.g. 304) or gateway (e.g. gateway 110) mayconnect to in order to adopt or connect with the network devices. Thenetwork device 304 may connect to the setup access points of new networkdevices 608, 610 and 612, as shown in FIG. 8. In other words, networkdevice 304 may communicate with new network devices 608, 610 and 612(e.g. via their setup access points). For example, as noted, networkdevice 304 may transmit a request/query to new network devices 608, 610and 612 to obtain identification information from new network devices608, 610 and 612. Identification information may include anyinformation/data that identifies the network device, such as the networkdevice's SSID, MAC address, serial number, defining characteristic orfunctionality, among others.

In an alternative embodiment, gateway 110 or an existing network device,such as device 304, may generate a setup access point (instead of or inaddition to, for example, a new network device). For example, gateway110 or device 304 may generate such an access point and then leave it onsuch that it may scan for new network devices to allow such new networkdevices to connect to it. The new network device may also open a setupaccess point, and gateway 110 or device 304 may connect to its setupaccess point to, for example, receive its identification information.

FIG. 9 illustrates an example of a local area network 900 including agateway and a network device connected to three new network devices,according to embodiments of the present invention. FIG. 9 alsoillustrates an access device 108 in communication with network device304. After network device 304 searches for, finds, and connects to newnetwork devices 608, 610 and 612 (e.g. via their setup access points),new network devices 608, 610 and 612 may transmit identificationinformation (and possibly other information) to network device 304.Network device 304 may then aggregate the identification informationreceived from new network devices 608, 610 and 612 into a single dataset, table, database, or other data aggregation/storage medium.

The network device (or any other device to aggregate such information)may perform analysis on the identification information. For example, theidentification information may be analyzed to determine commonfunctions, characteristics, or other identifying features of each of thenetwork devices for which identification information was received.Analysis may also be performed to find common capabilities or functionsof the network devices, or other comparison data points between thenetwork devices' identifications.

Although network device 304 may be connected to new network devices 608,610 and 612 such that network device 304 may receive identificationinformation from new network devices 608, 610 and 612, new networkdevices 608, 610 and 612 may not have joined network 900 such that newnetwork devices 608, 610 and 612 may be free to communicate with gateway110 and other devices on the network. More specifically, network device304 may generate/establish a connection with new network devices 608,610 and 612 (e.g. via their setup access points), but not allow them tojoin the network until new network devices 608, 610 and 612 have beenauthenticated to join the network. For example, network device 304 (orgateway 110) may authenticate new network devices 608, 610 and 612, byconfirming that new network devices 608, 610 and 612 are allowed to jointhe network, after network device 304 (or gateway 110) receives arequest to join the network from new network devices 608, 610 and 612.

There are several ways in which network device 304 may authenticate newnetwork devices 608, 610 and 612. For example, network device 304 maytransmit the (e.g. aggregated) identification information received fromnew network devices 608, 610 and 612 to access device 108. Once theidentification information (which is associated with new network devices608, 610 and 612) is received from network device 304, access device 108may use the identification information to generate one or moreauthentication queries to authenticate one or more of new networkdevices 608, 610 and 612. More specifically, access device 108 maydisplay the identification information to the display/interface ofaccess device 108 such that the identification information will bepresented to a user of the access device. The identification informationof new network devices 608, 610 and 612 may be presented as received bynetwork device 304 from new network devices 608, 610 and 612 or may bemanipulated to be presented in a user-friendly manner. For example, theidentification information may be presented in a list of new networkdevices so as to allow the user to select the network devices that theuser wishes to authenticate to join the network. Specific examples ofuser interface displays of access device 108 are described and shownfurther with respect to FIGS. 19 and 20.

After the identification information of new network devices 608, 610 and612 is displayed at a user interface of access device 108, access device108 may receive inputs from a user of the access device indicating oneor more answers to the query or queries related to authentication of newnetwork devices 608, 610 and 612. For example, a user may select certaindevices of new network devices 608, 610 and 612 to authenticate, mayselect all of new network devices 608, 610 and 612 to authenticate, ormay select none of new network devices 608, 610 and 612 to authenticate.Upon selecting one or more new network devices 608, 610 and 612 toauthenticate, access device 108 may transmit one or more communicationsor responses to the queries/requests from network device 304 indicatingwhich of new network devices 608, 610 and 612 have been authenticated tojoin the network. The user may select the network devices toauthenticate and also select a “send” or “submit” button on accessdevice 108, or access device 108 may send responses to network device304 immediately upon receiving inputs from the user.

A user may also select an option for gateway 110 to not requireauthentication to allow a device, such as new network devices 608, 610and 612, to join network 1000. For example, gateway 110 may includesettings such that gateway 110 may allow, without authentication, anydevice or a subset of all devices to connect to gateway 110 and/or joinnetwork 1000.

Other methods are possible to authenticate new network devices 608, 610and 612 before they are allowed to join the network. For example,existing network device 304 or gateway 110 may have previously storedauthentication information related to new network devices 608, 610and/or 612. For example, cloud network 114 may have transmitted/sentinformation related to new network devices 608, 610 and 612 to gateway110, which gateway 110 may have then transmitted to network device 304.Such information, received by gateway 110, may includepre-provisioning/authentication information indicating to gateway 110(and network device 304) that new network devices 608, 610 and 612 areallowed to join local area network 1000. Cloud 114 may have previouslyreceived this pre-authentication information from a user (e.g. viaaccess device 108). Therefore, gateway 110 or existing network device304 may query an internal storage device or elsewhere within the networkto confirm that new network devices 608, 610 and 612 are authenticatedto join the network 1000.

In another alternative embodiment, network device 304 may send/transmita query to external cloud network 114 including a request for externalcloud 114 to indicate to gateway 110 whether network device 502 shouldbe allowed/authenticated to join the network 1000. External cloudnetwork 114 may have stored such authentication information because itmay have received such information access device 108 or elsewherepreviously. External cloud network 114 may transmit/send a response tothe query from network device 304 (or gateway 110) including informationindicating whether or not new network devices 608, 610 and 612 areauthenticated to join the network.

FIG. 10 illustrates an example of a local area network 1000 including agateway and six network devices, according to embodiments of the presentinvention. After new network devices 608, 610 and 612 have beenauthenticated, new network devices 608, 610 and 612 may be connected toor join network 1000. As such, new network devices 608, 610 and 612 maybe connected to existing network devices 302, 304 and 306, as well asgateway 110 and external cloud network 114. For example, one or more ofnetwork devices 302, 304 and 306 may generate a communicationconnection/path with one or more of new network devices 608, 610 and612.

FIG. 11 illustrates an example of a local area network 1100 including agateway and six network devices, according to embodiments of the presentinvention. As noted, certain network devices, and any devices that areconnected to the network 1000 via the network devices, may be controlledremotely by, for example, an access device, such as access device 108shown in FIG. 11. If multiple network devices, such as network devices608, 610 and 612 are powered on and/or attempt to connect to network1000 at the same time, network devices 608, 610 and 612 may be relatedto or associated with one another in some way. For example, networkdevices 608, 610 and 612 may be located in the same room of a building.More specifically, network devices 608, 610 and 612 may each beconnected to a light bulb where each of the light bulbs connected tonetwork devices 608, 610 and 612 are located in the same room.Therefore, it may be beneficial for a user to turn on or off the lightbulbs connected to network devices 608, 610 and 612 at the same time(or, for example, if network devices 608, 610 and 612 are light bulbsthemselves, then it may be beneficial for a user to turn on or offnetwork devices 608, 610 and 612). In order for a user to control suchnetwork devices at the same time, the devices may be grouped together ina grouping, such as grouping 1180, such that they are treated within thenetwork as a single virtual device. For example, a user may controlgrouping 1180, which includes network devices 608, 610 and 612, bypressing one button for all three devices to perform a function insteadof having to press one button for each of the devices to perform thatfunction.

As noted with respect to FIG. 7, gateway 110 may facilitate the processof connecting the new network devices 608, 610 and 612 to the network,and the network may not include network devices already connected to thenetwork when new devices connect to the network, such as network devices302, 304 and 306, as shown in FIG. 6. Therefore, similar to grouping1180 in FIG. 11, new network devices 608, 610 and 612 may be grouped ina grouping, such as grouping 1280. Similarly, grouping 1280 may becontrolled remotely outside the network 1200 via access device 108.

Many reasons may exist why multiple new network devices may be poweredon at substantially the same time. For example, a user may purchasemultiple light bulbs and plug them in into light sockets over the courseof a short period of time. Therefore, in some circumstances, networkdevices that are powered on at substantially the same time may bemultiple devices of the same type. In another example, the user may havegone on a shopping trip and purchased several different devices, some ofwhich may be of different types (e.g. a light switch and a motion sensorand a DVD player). However, the user may arrive home and power on thedifferent devices at substantially the same time soon after arrivinghome. Therefore, in some circumstances, network devices that are poweredon at substantially the same time may be of different types.

Furthermore, although sometimes devices, whether of the same type (e.g.multiple lights) or of different types (e.g. a light and a sensor) maybe powered on, and therefore attempt to connect to the network, such asnetwork 1100, at substantially the same time, other devices may bepowered on and connect to the network at different times. For example,network devices 302, 304 and 306 had already been connected to network600 by the time new network devices 608, 610 and 612 attempted to joinnetwork 1100. A user may start a network by purchasing a gateway andnetwork devices to connect to the network, and then at a later timepurchase more network devices and/or more gateways to connect to thenetwork and the existing network devices and gateway(s) on the network.Similarly, certain devices may be included in a group, such as group1280 in FIG. 12, and other devices may be added to the group at a latertime. For example, if one or more of network devices 302, 304 and 306are in a device group and, as shown in FIG. 11, network devices 608, 610and 612 are later added to network 1100, one or more of devices 608, 610and 612 may be added to the existing group including one or more ofdevices 302, 304 and 306. Furthermore, one or more of new networkdevices 608, 610 and 612 may be included a new group, such as group1280.

As shown in FIGS. 11-12, network devices that are of the same type (e.g.a plurality of light bulbs) may be grouped together. For example, a setor group of light bulbs may have the same functionality. Morespecifically, a set of lights may include the single two-wayfunctionality of turning on and off. However, as shown in FIG. 13,devices of different or disparate types may also be grouped togetherinto device groups.

FIG. 13 illustrates local area network 1300, according to embodiments ofthe present invention. Local area network 1300 includes two light bulbs1308 and 1312 and a motion sensor 1310. Light bulbs 1308 and 1312 andmotion sensor 1310 may be connected to network 1300 via network devices.In other words, network devices, such as network devices 608, 612 and610 (as shown in FIG. 9, for example) may be connected to network 1300(and therefore to gateway 110), and light bulbs 1308 and 1312 and motionsensor 1310 may be connected to network devices 608, 612 and 610,respectively.

Although light bulbs 1308 and 1312 are a different type of device asmotion sensor 1310, light bulbs 1308 and 1312 and motion sensor 1310, orthe network devices that connect light bulbs 1308 and 1312 and motionsensor 1310 to network 1300, may still be included in the same devicegroup. Disparate devices, such as a light bulb (e.g. bulb 1308 and 1312)and a motion sensor (e.g. sensor 1310) may be included in the samedevice group if the devices are capable of the same functionalitybetween the disparate devices. For example, light 1308 and sensor 1310may each include the functionality of turning on and off. Furthermore,it may be beneficial to the user to turn on or off light 1308 and sensor1310, such as if sensor 1310 is a motion sensor that turns on light 1308when it detects motion, at the same time. Therefore, such devices may beincluded in the same group so as to allow a user to control the devicesbased on their common functions.

Although disparate devices may include the same or similarfunctionality, it may still not be beneficial for a user to group suchdevices together. For example, although a light and a coffee maker mayeach be capable of turning on and off, a user may not want to turn off acoffee pot if it is in use and in the process of making coffee at thesame time it wants to turn off a light in the same room. Therefore, auser may choose to restrict certain devices from being grouped together.Such a restriction may be predetermined before such devices areconnected to the network, or a rule to restrict such a grouping may becreated by the user after the devices have been connected to thenetwork.

Although disparate devices may be grouped in the same group, asdescribed with respect to FIG. 13, devices may be capable of a differentset of functionality that other devices in their respective groups arenot capable of A device or the network may become confused when thedevice receives a command or request to perform a certain function. Adevice may fail to perform a certain function because the device iscapable of alternative functions for which it did not receive a command.For example, device 1308 may be a light switch that turns on and off,but may also include the functionality of a dimmer, while device 1312may be a light switch that turns on and off, but does not include anyother functionality. The network and/or one or more of devices 1308 and1312 may become confused and/or fail to perform one or more functionsbecause they do not include the same set of functions because thenetwork and/or devices may not understand commands received from theaccess device and/or network (e.g. network 1300 or cloud network)directed to only one function of the device.

Several techniques are possible to avoid such a problem. First, thedevice, network, or group may deactivate the functions of the devicesthat are not common to all devices in the group. In other words, thegroup may detect (and therefore be able to be controlled regarding) aset of functions that are the least common denominator functions of thedevices in the group and deactivate the other device functions of thedevices in the group. In an alternative embodiment, the device, network,or group may automatically pull the device that includes additionalfunctions out of the group. For example, if a user selects a device tobe placed into a new or already existing group, or if the access deviceand/or network automatically selects the device to be placed into a newor already existing group, the network and/or device may detect that thedevice includes additional functionality that the other devices in thegroup do not have and remove the device from the group. The deviceand/or network may also decide to not include a device in a group (e.g.during an automatic grouping process) because of its functionality thatmay be disparate from the other devices in the group.

In another alternative embodiment, an alternative functionality mayreplace one or more of the common functionalities that make up thegroup. For example, new device 1 in FIG. 11 includes the functionalityof a light dimmer. Therefore, the light includes various levels of lightincluding on, off, and various levels of light in between as decided bythe dimmer or a user changing the dimmer setting. Therefore, a certaindimmer setting may replace the “on” or “off” setting that the groupviews as common to each of the devices in the group. For example, thedevice may, within the confines of the group, turn “off” and to“dimmed”. The “dimmed” function may be at whatever selected dimmed stateis chosen by the user (e.g. 70% dimmed). In other words, when a commandis given to each of the devices in the group to turn on, most devices inthe group turn fully on and the device that includes a dimmer turns tothe dimmed state chosen by the user. In order to change the dimmed statefrom a first dimmed state to a second dimmed state, the access devicemay be able to give the user temporary access to the dimmer setting soas to allow the user to change the dimmer setting. The dimmer may alsobe changed in certain embodiments from the physical dimmer switch at thelight.

In another alternative embodiment, the devices in the group that includefunctions that other devices in the group are not capable of may notrespond to requests or commands to perform that function. For example,if the user, access device or network sends a request to new devices 1,2 and 3 to dim their lights, devices 2 and 3 may not respond to therequest because they do not have dimming capability. On the other hand,device 1 may respond to the request because it does have dimmingcapability.

A group may be created in different ways. For example, a user of anaccess device controlling network devices on the network may create agroup and/or edit a group using the access device. Such examples arefurther discussed with respect to FIGS. 19-20. Alternatively, devicegroups may be created using automatic grouping. Devices may be groupedautomatically, without user intervention, by an access device (such asaccess device 108), a network device or another device on the local areanetwork (such as a gateway e.g. gateway 110), a cloud network (such ascloud network 114), or a device external to the network (although whenreferred to herein such a device capable of automatic grouping may bereferred to as an access device, it should be understood that any of thedevices described herein may perform automatic grouping methods).Automatic grouping includes the process of grouping devices within anetwork into groups based on the common functions or capabilities thateach device is able to perform and other factors that make the controlof multiple devices together, as a single virtual device, convenient.

A device, such as an access device, may determine, withoutintervention/input from a human user, which devices are able to be orshould be grouped together in the same device group, by compiling a setof functions that each device is capable of performing. The device maystore the compiled functions in a list. In order to determine whichfunctions a device is capable of, the access device may communicate withthe network device. For example, the access device may transmit acommunication to the device requesting an indication (e.g. a list) ofthe functions that the network device is capable of performing. Thedevice may respond to the query with a communication including anindication of the functions that it is capable of performing.Information about what functions a device is capable of performing mayalso be communicated to the access device, or whichever device isperforming automatic grouping, while the device is in the process ofjoining and/or being authenticated to join the network. For example, asnoted with respect to FIG. 6, when a network device is powered on, asetup access point (e.g. wireless access point), such as setup accesspoints 609, 611 and 613, is generated by the device to allow devices onthe network to connect to the new device using WiFi or other standards.Furthermore, identification information and other information may besent by the new network device to a device on the network, such as agateway, via the network device's setup access point. Included in suchinformation sent to the network during setup may be information relatedto the functions that the device is capable of performing. However, suchinformation may be communicated to other devices on the network, anaccess device connected to the device, a cloud network, etc. at anyother time during or after the device joining the local area network.

A device, such as an access device, may obtain information related tothe functions that a device may be able to perform in alternative ways.For example, a network device may be able to compile such functionsrelated to another (e.g. new) device due to its personal interactionwith the device. For example, a motion sensor that is connected to alight may know that the light is capable of turning on and off and mayalso know that the light includes a dimmer such that a user may dim thelight to a lighting amount less than 100% of its capability. The accessdevice, or other device performing automatic grouping including thelight, may receive information regarding the light's capabilities fromthe motion sensor. Furthermore, as noted with respect to FIG. 4, deviceson the network may share information with each other regarding thestatus and/or performance of other devices on the network. Capabilityinformation regarding a device may be shared among devices on thenetwork, and therefore an access device may obtain such capabilityinformation regarding a network device from any device on the network,from a cloud network connected to the network, or from any other devicethat had previously obtained such information.

Furthermore, device groups may be determined by the geographic locationof each device being considered. For example, multiple devices may beplaced in a group, and therefore controlled together at the same time,because they are all located in the same area of a structure or in thesame room of a building.

FIG. 14 shows a house with two rooms and network devices in each roomthat may be grouped, according to embodiments of the present invention.FIG. 14 includes house 1400. House 1400 includes two rooms, room 1401and room 1402. Room 1401 includes network devices 302 and 304 and accessdevice 108. Network devices 302 and 304 are represented by lights inFIG. 14. However, network devices 302 and 304 may not be the lightsthemselves, but rather may be network devices that have lights or lightbulbs connected to the network devices. Room 1402 includes networkdevices 608, 610 and 612. Network devices 608 and 612 are represented bylights in FIG. 14. However, network devices 608 and 612 may not be thelights themselves, but rather may be network devices that have lights orlight bulbs connected to the network devices. Network device 610 isrepresented by a motion sensor. However, network device 610 may not bethe sensor itself, but rather may be a network device that has a motionsensor connected to the network device. It may be beneficial to groupnetwork devices 302 and 304 in room 1401 in the same grouping becausethey are in close proximity to each other (e.g. in the same room).Therefore, a user may choose to turn the lights connected to networkdevices 302 and 304 on or off at the same time. Similarly, it may bebeneficial to group network devices 608, 610 and 612 in the samegrouping because they are in close proximity to each other (e.g. in thesame room). Therefore, a user may choose to turn the two lights andsensor connected to network devices 608, 612 and 610, respectively, onor off at the same time.

Access device 108 may automatically detect that the devices in room 1401may or should be grouped together, and may automatically detect that thedevices in room 1402 may or should be grouped together. For example,access device 108 may initiate a process by which access device 108 maydetermine that the devices in a particular room are in the same room.More specifically, access device 108 may transmit a communication (e.g.a query) to all of the network devices in house 1400, including networkdevices 302, 304, 608, 610 and 612. The transmitted communication mayinclude a request for the network devices to each transmit back aresponse to the communication/query indicating that the network devicesreceived the communication from access device 108. The access device 108may determine how devices can/should be grouped based on their responsesto the query. For example, access device 108 may determine how devicescan/should be grouped based on how long it took to receive a responsefrom each network device. For example, if network devices aregeographically close to each other, the access device should receiveresponses from those network devices in approximately the same amount oftime. For example, access device 108 should receive a response fromnetwork devices 608, 610 and 612 at approximately the same time becauseeach of the three network devices are a similar distance away fromaccess device 108.

In an alternative embodiment for automatic grouping, access device 108may determine which devices should be grouped together related to theirgeographic location based on which circuits the network devices areconnected to (or which portion of a circuit the network devices areconnected to). More specifically, for example, access device 108 maydetermine that network devices 302 and 304 are connected to the samecircuit. For example, each of the network devices maybe connected toeach other via a wire, such as wire 1470. As shown in FIG. 14, networkdevices 302, 304, 608, 610 and 612 are all connected to wire 1470.Therefore, if access device 108 or another device initiates a signal(e.g. a query) to be sent through wire 1470 including a responserequest, access device 108 could again determine the approximaterelative location of each network device based on their response time.

The access device may initiate such a process on a periodic basis. Sucha periodic repeating of this process may allow the access device toperiodically assess the grouping profile of the system, and may allowthe access device to (automatically or otherwise) adjust the groupingprofile (e.g. switch a device from to a different group, remove a devicefrom a group, add a new device to a group, etc.) based on changes in thenetwork's topology and communication abilities.

Other methods are possible for detecting which devices should be groupedtogether. For example, an access device may detect which devices shouldbe grouped together based on which devices are turned on/off at the sametime. Since a switch may control the on/off function of multiple networkdevices, the network devices may be turned on/off at the same timeregularly. Therefore, the access device may detect such a pattern, andanalyze such behaviors of the network devices to determine that thenetwork devices should be grouped together in the same group. Morespecifically, an access device may receive signals/communications fromeach network device when it performs a function. For example, the accessdevice may receive a notification any time the switch isflipped/switched and/or any time any of the network devices areactivated or turned on/off (e.g. light turns on/off). The access devicemay compile those performed functions for each device over time andstore a list or database of those functions and information related toeach function (time, between which devices, etc.).

An access device may also sense/analyze other similar behaviors of othernetwork devices without the use of a switch that controls both networkdevices and therefore causes the network devices to turn on/off at thesame time on a regular basis. For example, the access device may detectthat a sensor is activated at the same time that lights are turned on.Since such network devices are activated or turned on at the same time,the access device may determine that those three network devices areassociated with each other, and therefore should be grouped together.For example, an access device may know that a network device is or isconnected to such a sensor and may detect motion directly that causesthe network devices to turn the lights on. Analysis of such observationsmay also cause the access device to determine that network devicesshould be grouped together in the same group.

In another example, a device may determine that a certain group ofnetwork devices should be grouped together based on the date they werepurchased. A device may determine that a certain group of networkdevices should be grouped together based on the date they were connectedto the network. Such a decision may also be based on the serial numberassociated with each device. For example, the serial numbers may beassigned to devices in chronological order. Network devices maycommunicate their serial numbers to the network upon entering thenetwork, or the access device may detect the serial number on thedevice.

There are alternative ways for a user to group devices using the devicesthemselves. For example, the user may direct the access device totransmit a communication to certain network devices (e.g. the networkdevices in a room) including a request for the network devices to takean action. For example, the communication may request that multiplelight bulbs turn on and then turn off within a short amount of time(i.e. a flicker with a predetermined or non-predetermined pattern). Anetwork device may utilize an LED on the device if the device does nothave a bulb. The access device may be able to detect such actions takenby the network devices, and may subsequently group the network devices(that took action) in the same group. Furthermore, a user may use nearfield communication to, within a predetermined amount of time, initiatea communication between the access device and each network device thatthe user would like to be grouped together. The access device maysubsequently group the chosen network devices in the same group.Alternatively, a camera or video camera (of the access device orotherwise) may be used to detect network devices in a certain geographicarea. For example, an access device may take a picture of a room anddetect which network devices are present in the room (either because ofa marking or an action taken by the devices) and group the set ofdevices or a subset of the devices in the same group. In anotherexample, a video camera on the access device may video tape multiplelight bulbs in the same room initiating a blinking pattern, causing theaccess device to recognize the network devices. The blinking pattern mayrepresent serial number associated with the respective devices, or thedevices may broadcast their serial numbers using a different method. Theaccess device may subsequently place the detected network devices in adevice grouping.

Generally, access device 108 may, by controlling the network devices onthe network and observing their functions and actions over time and inrelationship to each other, determine which devices can/should begrouped together in the same device groups. It may also be beneficial touse a combination of the methods described herein to determine whichdevices may or should be combined into a group, as one method may notyield the most ideal grouping results by itself.

Furthermore, access device 108 may automatically correct a previouslygrouped set of network devices. For example, a grouping profile, made upof one or more groups, may be automatically adjusted if a new networkdevices enters the network, if an existing network device leaves thenetwork, if a network device is replaced with a network device that iscapable of different functions, if a network device loses one or more ofits functions (e.g. a function that is common among the network devicesin its group), among other reasons. A user of access device 108 mayselect a setting within the access device to indicate to the accessdevice whether the user wants the access device to automatically updatebased on such changes in the network. Alternatively, the access devicemay present a query or notification to the user each time the networkchanges (e.g. new network device present, network device left thenetwork, etc.) so that the user may choose whether to allow the accessdevice to update or whether the user would like to control changes tothe grouping profile based on the change in network topology. Forexample, as noted, a set of devices (e.g. multiple light bulbs) may begrouped together (including their respective network devices) based onan observation by the access device that the light bulbs turn on and offat the same time. However, if one of the light bulbs stops turningon/off along with the rest of its group, the access device may assumethat the device was removed, that the switch that controls the devicewas adjusted to not control that light, or that a renovation took place.Based on that observation, the access device may automatically elect toremove that device from the group. Alternatively, the access device maysend a query or notification to the user via its display indicating thatsuch a change took place with respect to that light, and ask the userhow the user would like the system to respond.

If a network device is removed from a group, the group may be controlledby additional functionality for which the group may not previously havebeen able to be controlled. For example, if a group is being controlledusing a set of functions determined to be the least common denominatorof the devices in the group (and deactivated the other device functionsof the devices in the group for purposes of control), and the removeddevice prevented certain functions from being a part of the least commondenominator set of functions, the set of functions for control of theremaining devices may adjust to add those functions. More specifically,if three devices, including two light bulbs with dimmers and one motionsensor were in a group, the least common denominator set of functionsmay include only the devices' on/off capability (and the dimmingcapability/functions of the lights and any other functions of the sensormay be disabled). However, if the motion sensor is removed from thegroup, the least common denominator set of functions across theremaining devices, two light bulbs, may include the dimming capabilityof the lights. Therefore, the access device or other device controllingthe group profiles may automatically/dynamically add the dimmingfunction to the functions able to be controlled by the access device. Inan alternative embodiment, the access device may transmit a prompt/queryto the display/user asking the user whether the user would like tocontrol the new common functionality (i.e. dimming of the two lightdevices).

Devices may also be pre-grouped before being purchased by a user. Forexample, certain devices may be purchased with a predetermined groupingprofile such that the user may not need to generate new groupings orperform automatic grouping related to those devices. For example, a setof light bulbs may be divided into two or more groups (and, for example,either sold as a set or give the purchaser/user the ability to buy asmany of each group as they choose) so that the purchase may place thegrouped light bulbs in, for example, separate rooms. Therefore, when theuser attempts to control the devices using an access device, the devicesmay already be grouped according to the purchasing choices of the user.The devices may be pre-grouped by, for example, registering such groupsin the firmware of each device. The access device may allow the user toedit the predetermined groups at a later time by adding, subtracting, orshifting network devices to/from the device groupings.

FIG. 15 illustrates an example of a local area network 1500 including agateway and three network devices connected to three new networkdevices, according to embodiments of the present invention. As notedwith respect to FIG. 9, new network devices 608, 610 and 612 maytransmit identification information (and possibly other information) toan existing network device, such as network device 304. Network device304 may then aggregate the identification information received from newnetwork devices 608, 610 and 612, and may then send the identificationinformation, either aggregated or individually, to access device 108.However, the identification information corresponding to or associatedwith the new network devices 608, 610 and 612 may be each transmitted toa different existing network device, such as network devices 302, 304and 306. More specifically, after new network devices are powered orturned on and generate their individual setup access points, one of theexisting network devices, such as network device 304, may detect thateach of the new network device 608, 610 and 612 are associated withnetwork 1500. Network device 304 may then transmit a communication tothe other existing network devices, such as network devices 302 and 306,regarding new network device 608, 610 and 612. More specifically,network device 304 may then transmit a communication to network devices302 and 306 requesting that network devices 302 and 306 each connect toa new network device (e.g. via the setup access point for a new networkdevice). Since each network device may only connect (i.e. be connectedto a WiFi channel shared by the new network device, or that the setupaccess point of the new network device is transmitting across) to onenew network device at a time, three different network devices connectingto three different new network devices at the same time allows for thenew network devices to connect to the network and transmit theiridentification information in parallel, saving time and efficiency.Therefore, as shown in FIG. 15, existing network device 302 may connectto new network device 608, existing network device 304 may connect tonew network device 610, and existing network device 306 may connect tonew network device 612.

In an alternative embodiment, a single network device may not be thefirst existing network device to detect a signal or request from a newnetwork device to join the network. Instead, each existing networkdevice may be in closest proximity to one of the new network devices andmay therefore detect the new network device in its area. As such, eachnew network device may connect (e.g. via its setup access point) to anexisting network device on its own.

FIG. 16 illustrates an example of a local area network 1600 including agateway and three network devices connected to three new networkdevices, according to embodiments of the present invention. As noted,existing network device 302 may connect to new network device 608,existing network device 304 may connect to new network device 610, andexisting network device 306 may connect to new network device 612. Assuch, new network device 608 may transmit its identification informationto existing network device 302, new network device 610 may transmit itsidentification information to existing network device 304, and newnetwork device 612 may transmit its identification information toexisting network device 306. Thereafter, network devices 302 and 306 maytransmit the identification information it received from itscorresponding new network device to network device 304 so that networkdevice 304 may transmit the identification information for all three newnetwork devices to access device 108, as described with respect to FIG.9. Alternatively, each existing network device may transmit its receivednew network device identification information to access device 108 onits own. After access device 108 receives identification informationassociated with each of new network devices 608, 610 and 612, accessdevice 108 may use the identification information to authenticate thenew network devices. More specifically, access device 108 may use theidentification information to generate one or more authenticationqueries (or an authentication in another form) to authenticate one ormore of new network devices 608, 610 and 612. More specifically, accessdevice 108 may display the identification information to thedisplay/interface of access device 108 such that the identificationinformation will be presented to a user of the access device. Theidentification information of new network devices 608, 610 and 612 maybe presented as received by network device 304 from new network devices608, 610 and 612 or may be manipulated to be presented in auser-friendly manner. For example, the identification information may bepresented in a list of new network devices so as to allow the user toselect the network devices that the user wishes to authenticate to jointhe network.

After the identification information of new network devices 608, 610 and612 is displayed at a user interface of access device 108, access device108 may receive inputs from a user of the access device indicating oneor more answers to the query or queries related to authentication of newnetwork devices 608, 610 and 612. For example, a user may select certaindevices of new network devices 608, 610 and 612 to authenticate, mayselect all of new network devices 608, 610 and 612 to authenticate, ormay select none of new network devices 608, 610 and 612 to authenticate.Upon selecting one or more new network devices 608, 610 and 612 toauthenticate, access device 108 may transmit one or more communicationsor responses to the queries/requests from network device 304 indicatingwhich of new network devices 608, 610 and 612 have been authenticated tojoin the network. The user may select the network devices toauthenticate and also select a “send” or “submit” button on accessdevice 108, or access device 108 may send responses to network device304 immediately upon receiving inputs from the user.

FIGS. 17 and 18 illustrate an example of a local area network includinga gateway and a network device connected to three new network devices,according to embodiments of the present invention. As noted with respectto FIG. 9, new network devices 608, 610 and 612 may transmitidentification information (and possibly other information) to anexisting network device, such as network device 304. Network device 304may then aggregate the identification information received from newnetwork devices 608, 610 and 612, and may then send the identificationinformation, either aggregated or individually, to access device 108.However, the identification information corresponding to or associatedwith the new network devices 608, 610 and 612 may be each transmittedbetween new network devices in a chain. As shown in FIG. 17, new networkdevices may connect to each other, one after another. For example, afterexisting network device 304 detects that new network devices 608, 610and 612 are present and/or are associated with network 1700, networkdevice 304 may transmit location or other information regarding thepresence of new network devices 610 and 612 to new network device 608and request identification information from new network devices 610 and612. Thereafter, network device 608 may transmit its identificationinformation back to network device 304, as shown in FIG. 18, and mayalso transmit identification or other information regarding the presenceof new network device 612 to new network device 610 along with a requestfor their identification information. Thereafter, new network device 610may transmit its identification information back to network device 608(which may then transmit that information back to network device 304, asshown in FIG. 18), and may also transmit a request for identificationinformation from new network device 612. Thereafter, new network device612 may transmit its identification information back to new networkdevice 610 (which may then transmit that information back to networkdevice 304 via new network device 608, as shown in FIG. 18). Such achain may cause network device 304 to obtain identification informationfrom each new network device while only connecting to one of the newnetwork devices (or, alternatively, to the setup access point of thatnew network device).

Although this embodiment of the present invention is described withrespect to a single chain of new network devices, different numbers ofchains may be possible. For example, two different chains of new networkdevices, for transferring identification information back to a networkdevice on the network, may connect to (i.e. start from) existing networkdevice 304 or to new network device 608. Such chains may be based ongeographic proximity, network proximity, or other factors.

In such an embodiment, because the identification information fordifferent network devices may travel between different numbers ofnetwork devices, the identification information of different new networkdevices may take a different amount of time to reach existing networkdevice 304. Such a delay may be already known by existing network device304 (or any other device that detects the new network devices) becauseit requested the chain of communications to be created in the firstplace. However, other devices in the chain may not know how many devicesare in the chain(s) or their locations and how such factors may affectthe time it may take for transmissions (e.g. of identificationinformation) to travel back through the chain to the network. However,network device 304 (or any other device that detects the new networkdevices) may transmit, along with the request(s) it sends to the firstnew network device in a respective chain, an indication of the locationand/or other information related to each of the new network devices.Alternatively, network device 304 may transmit a request for each newnetwork device to wait a specific amount of time to receiveidentification information or for new network devices to otherwisecommunicate with it before discontinuing communication within the chain.

FIGS. 19-20 illustrate exemplary embodiments of screenshots of anexemplary user interface (UI) display for an application on an accessdevice, according to embodiments of the present invention. However, theexemplary UIs are not limited to these example embodiments. In anembodiment of the invention, the visual interfaces illustrated in FIGS.19-20 are displayed on a mobile computing device, which can have a touchsensitive (i.e., touch screen) display device. For ease of explanation,the monitoring and control operations discussed below with reference toFIGS. 19-20 are described in the context of an application executing onan access device 108 with a touch-screen display device. However, theoperations are not intended to be limited to the exemplary device shownin FIGS. 19-20. It is to be understood that the user interfacesillustrated in the exemplary embodiments of FIGS. 19-20 can be readilyadapted to be rendered on displays of a variety of computing deviceplatforms running a variety of operating systems. Throughout FIGS.19-20, displays are shown with various tiles, interactive elements,icons, command regions, windows, toolbars, menus, and buttons that areused to initiate action, invoke routines, monitor network devices,control network devices, or invoke other functionality. The initiatedactions include, but are not limited to, displaying a state or status ofa network device, selecting a network device to control and/or monitor,setting a primary function of a network device, setting a secondaryfunction of a network device, and other inputs and gestures. Forbrevity, only the differences occurring within the figures are describedbelow.

FIG. 19 illustrates an exemplary user interface display 1900 for anapplication on an access device, according to embodiments of the presentinvention. FIG. 19 discloses a list of three exemplary network devices,including network devices 1908, 1910 and 1912, which have displays 1901,1902 and 1903, respectively, are assigned to devices 1918, 1920 and1922, respectively. Network device 1908 is connected to a light 1918,network device 1910 is connected to a motion sensor 1920, and device1912 is connected to a second light 1922. Network device 1908 (or thelight 1918) can be turned on by a user by pressing button 1928, networkdevice 1910 (or the light 1920) can be turned on by a user by pressingbutton 1930, and network device 1912 (or the light 1922) can be turnedon by a user by pressing button 1932.

When one or more new devices join the network, an access device maydetect that those new devices are present on the network. For example,the access device, if connected to the local area network, may send aquery or multiple queries over time to the gateway, which is connectedand/or communicates with each network device on the network, requestinga response or a notification of any new network devices that are presenton the network. If the access device is remote from the local areanetwork, the access device may send a query or multiple queries overtime to a cloud network, which is connected and/or communicates with thegateway and/or each network device on the network, requesting a responseor a notification of any new network devices. The access device may thendisplay the network device(s) on a display or user interface of theaccess device, such as display 1900.

The display of network devices, such as devices 1908, 1910 and 1912 mayinclude a request/query to authenticate each of the newly discoverednetwork devices. For example, display 1901 for device 1908 includes aquery 1948 that asks whether the device should be allowed to join thenetwork. Similarly, display 1902 for device 1910 includes a query 1950that asks whether the device should be allowed to join the network anddisplay 1903 for device 1912 includes a query 1952 that asks whether thedevice should be allowed to join the network. The user may then press orslide the button under each display's “Allow to Join” query to indicatewhether each device is authenticated to join the network. The user mayauthenticate all, some, or none of the network devices to join thenetwork. After the user selects an answer to one of the queriesassociated with one or more of the network devices, the access devicereceives the inputted answer and transmits a communication/notificationof the input from the user. The access device may transmit such aresponse/input to a gateway on the network or to an existing networkdevice on the network. The gateway or network device may then use thequery answers to decide whether or not to authenticate the new networkdevice(s), send the new network device(s) network information such asthe network's credentials, allow the new network device(s) to join thenetwork, etc. Alternatively, the access device may use the query answersto make such a decision, and then transmit a communication to thegateway or existing network device indicating the decision (e.g. if theuser answered “yes” to a query, a communication including a command tosend the network credentials to the new network devices).

As shown in FIG. 19, the user may also group the new network devicesinto either new groups (e.g. by pressing button 1942) or existing groups(by pressing grouping buttons 1944). The user may group the new networkdevices into a new group, for example, if the functions that the newnetwork device(s) are capable of do not match or fit with a currentlyexisting group. More specifically, after the user presses button 1942,the access device may create a new virtual group and store informationabout the virtual group (and any other groups) internally.Alternatively, the access device may send a communication to a cloudnetwork or other external storage regarding the creation of a new group,and may subsequently store information related to any network devicesthat are placed in the new group. For example, the access device and/orcloud network may create and store a table/list/chart that includes eachgroup and each of the network devices included in that group. The tablemay include the functions of each network device that is associated witheach group, since the reason that certain devices are grouped togethermay be because of the functions that each device can perform.

Various user interface techniques may be available for a user to add anew device to an already existing group. For example, a user may presson the tile representing a network device display and drag and drop thattile on top of a tile that represents an existing group. For example, auser may press on device display 1901 and drag that display until it isplaced over the “1. Upstairs Lights” tile, which represents an alreadyexisting group of lights in the upstairs of a house. Alternatively, auser may select an existing group (by, for example, pressing on anexisting group tile, such as an existing group tile), and thensubsequently touch the tiles associated with the network devices thatthe user would like to add to the group. Alternatively, the user maypress on the “edit” button 1950 to edit the existing groups. Forexample, after pressing edit 1950, check boxes may appear next to eachnew device so that the user may select the devices that the user wouldlike to place in an existing group. Thereafter, the checked devices maycollapse into a group together. Various other variations of these typesof user interface setups are also possible. Each time a user presses ona button within display 1500, a communication may be sent from theaccess device to the stored group information, whether internally or onan external storage device (e.g. cloud network, such as cloud network114). For example, the access device may transmit a communication to thecloud network to indicate that a new device has been added to an alreadyexisting group. The communication may include a command or request tomove the device information associated with the moved device to adifferent portion of the table or chart that includes the devicegrouping information. Similar transmission of communication between theaccess device and the storage device may occur each time a userpresses/touches the display to enter a command for the access device toperform.

As noted, the user may manually group the new network devices into suchgroups or may choose to have the new network devices automaticallygrouped. To automatically group, for example, the user may select ananswer “yes” to the “Auto Group?” query 1940, causing the access device(or cloud or other device connected to the access device) toautomatically group the new network devices or suggest a groupingprofile for the new network devices, which the user may then accept,reject or edit (e.g. by pressing edit button 1950).

In each exemplary embodiment in which a user adds a device to an alreadyexisting group, or in other words edits the group profile of the system,the access device may transmit a communication to the local or externalstorage that houses/stores the group profile information, including dataregarding the different existing groups, the network devices in eachgroup, the different functionality of each device, and the relationshipsbetween each of the devices and each of the groups. Furthermore, eachtime a user clicks on a group or device to view more information about agroup or device, the access device may transmit a request or query tostorage so that the access device may retrieve the device/group/profileinformation to display/present to the user on display 1900. Furthermore,various communications may be transmitted and received between theaccess device and storage and any other device (e.g. cloud network) thatmay be controlling/performing any automatic grouping function. Forexample, if a different device (other than the access device) isperforming the automatic grouping function, the access device may send arequest to that device to perform automatic grouping based on thenetwork devices that are existing on the network and any new networkdevices that have recently joined the network, along with anyinformation collected about the functions/capabilities of the networkdevices. The device performing automatic grouping may then transmit backto the access device information about its suggested grouping so thatthe access device may present the grouping information to the user onits display. If the user makes any edits/changes to the suggestedgrouping, the access device may transmit back to the automatic groupingdevice a communication indicating the changes made by the user so as toallow the device to learn and adapt regarding the user's preferencesand/or any judgment calls it made when preparing a suggested groupingprofile for the access device/user.

As described herein, new (or existing) network devices may be presentedto the user, for example via a display on an access device, for thedevice (automatically) or the user (manually) to decide which devicesshould be grouped together into existing or new groups. Since the accessdevice may determine which devices are present and what the functionsare of each of those devices, the access device may dynamically adjustthe presentation of the list of devices available to be grouped based onboth functions that each device is capable of and selections made by theuser. For example, if a user selects a device to be placed in a certaingroup, a access device may remove certain other devices from the displayor mark other devices as devices that are unable to be grouped with thedevice selected by the user. More specifically, for example, if anaccess device displays network devices that are or are connected to alight and a coffee maker, and if a user selects the device that is or isconnected to a light, the access device may remove the coffee makernetwork device from the display if the access device determined that,based on the capable functions of the light and the coffee maker, thelight and the coffee maker cannot or should not be grouped. Such adecision to not allow grouping of certain devices together may be basedon the functions of those devices and/or the capabilities of the accessdevice/system to control such devices at the same time. Instead ofremoving the coffee maker from the display completely, the access devicemay mark the device as being unable to be grouped with the selecteddevice, such as by graying out the display of the coffee maker device orplacing the display towards the bottom of the access device display in alist for devices that cannot be grouped with the selected device. Incertain embodiments, the access device may provide functionality at theaccess device for the user to override the choice of the access deviceto prevent the light and the coffee maker from being grouped.

As noted with respect to FIG. 19, the user may also group the newnetwork devices into either new groups (e.g. by pressing button 1942) orexisting groups (by pressing grouping buttons 1944). The user may selectwhether to group the new network devices, either manually orautomatically, at the same time (e.g. on the same display screen) aswhen it selects whether to allow the new network devices to join thenetwork. FIG. 20 illustrates an exemplary user interface display 2000for an application on an access device, according to embodiments of thepresent invention. Display 2000 is similar to display 1900, exceptinstead of just presenting a display of a query to the user regardingwhether the user would like to authenticate each new network device,display 2000 also includes a query for each new network device regardingwhether the user would like to group the new network devices. Forexample, the user may select (e.g. check off) the “Group?” query 1958with respect to new network device 1908 (and/or query 1960 with respectto new network device 1910 and/or query 1962 with respect to new networkdevice 1912) and then select (e.g. press) a button within buttonsdisplay 1944 of the group that the user would like the selected newnetwork device to join. Alternatively, the user may select multiple newnetwork devices (by checking off the “Group?” query for multipledevices) and also select “yes” as an answer to the “Auto Group?” query1940, causing the access device (or cloud or other device connected tothe access device) to suggest a grouping profile for the selected newnetwork devices. Since the user may both authenticate and group newnetwork devices on one display, the user may more efficiently join andorganize such new network devices.

The embodiments of the present invention described herein are describedwith respect to certain numbers of “existing” and “new” network devices(e.g. three existing and three new). However, the embodiments of thepresent invention could be performed with, for example, only twoexisting and two new network devices, or any other number of each typeof device.

FIG. 21 is a flow chart 2100 showing an exemplary process for a networkto setup multiple network devices, according to embodiments of thepresent invention. Step 1202 includes receiving, at an existing networkdevice on a network, one or more communications, wherein the one or morecommunications include an indication that multiple new network devicesare associated with the network. For example, network devices may, asdescribed herein, open a setup access point through which an existingnetwork device may connect to the network device(s). Such a setup accesspoint may communicate with its surrounding area and devices in that areathat the device has been powered on and is ready to join a network.After one or more network devices have connected to an existing deviceon a network, the devices may transmit identification informationrelated to the network device to an existing network device so that theexisting device on the network and the network may know who the networkdevice is. Furthermore, such information may allow the existing deviceand the network to authenticate the device trying to connect to it.

Step 1204 includes receiving an indication that the multiple new networkdevices have each generated a setup access point. Step 1206 includesestablishing a connection with the setup access point of each of themultiple new network devices. Step 1208 includes receivingidentification information, wherein the identification informationincludes information identifying each of the multiple new networkdevices. And step 1210 includes transmitting the identificationinformation identifying each of the multiple new network devices,wherein when the identification information is received, theidentification information facilitates generating one or moreauthentication queries to authenticate one or more of the multiple newnetwork devices.

FIG. 22 illustrates an example of a front view of a network device 2200.FIG. 23 illustrates an example of a side view of the network device2200. The network device 2200 may include any of the network devices102, 104, or 106 described herein. In some embodiments, the networkdevice 2200 may be a home automation network device. For example, thenetwork device 2200 may include a home automation switch that may becoupled with a home appliance. A user may wirelessly access the networkdevice 2200 in order to access, control, and/or configure various homeappliances located within the user's home. For instance, the user mayremotely control appliances such as a television, radio, light,microwave, iron, space heater, wall A/C unit, washer, dryer, fan, and/orthe like.

In some embodiments, the network device 2200 may include a WiFi enabledswitch that connects home appliances and other electronic devices to acompatible 802.11b/g/n/ac WiFi network. The network device 2200 may thusallow users to locally or remotely turn devices on or off from anywhere,program customized notifications, and/or change device status. Thenetwork device 2200 may further allow a user to create custom schedulesor have devices respond to sunrise or sunset.

The network device 2200 includes an power switch 2202 that may bedepressed in order to turn the network device 2200 on and off. In someembodiments, a light source may be integrated with or located behind thepower switch. For example, a light-emitting diode (LED) may be locatedon a circuit board under the power button 2202. The light source may beilluminated when the network device 2200 is powered on, and may not beilluminated when the network device 2200 is powered off.

The network device 2200 further includes a communications signalindicator 2204. The signal indicator 2204 may indicate whether thenetwork device 2200 has access to a communications signal, such as aWiFi signal. For example, the signal indicator 2204 may include a lightsource (e.g., a LED) that illuminates when the network device 2200 isconnected to a communications signal. The light source may depictdifferent colors or other characteristics (e.g., flashing, dimming, orthe like) to indicate different levels of signal strength or mode ofoperation.

The network device 2200 includes a restore button 2310. The restorebutton 2310 may allow a user to reset the network device 2200 to factorydefault settings. For example, upon being depressed, the restore button2310 may cause all software on the device to be reset to the settingsthat the network device 2200 included when purchased from themanufacturer.

The network device 2200 further includes a plug 2308 and an outlet 2206.The plug 2308 allows the network device 2200 to be plugged into a wallsocket, such as a socket providing 120V, 220V, or the like. In turn, anappliance may be plugged into the outlet 2206. Once the network device2200 is registered according to the techniques described above, anappliance plugged into the socket 2206 may be controlled by a user usingan access device (e.g., access device 108).

FIG. 24 is an example of a block diagram of the network device 2200depicting different hardware and/or software components of the networkdevice 2200. As described above with respect to FIGS. 22 and 23, thenetwork device 2200 includes the outlet 2206, the plug 2308, the powerbutton 2202, the restore button 2310, and the communications signalindicator 2204. The network device 2200 also includes light source 2428associated with the power button 2202. As previously described, thelight source 2428 may be illuminated when the network device 2200 ispowered on.

The network device 2200 further includes a relay 2410. The relay 2410 isa switch that controls whether power is relayed from the plug 2308 tothe outlet 2206. The relay 2410 may be controlled either manually usingthe power button 2202 or remotely using wireless communication signals.For example, when the power button 2202 is in an ON position, the relay2410 may be closed so that power is relayed from the plug 2308 to theoutlet 2206. When the power button 2202 is in an OFF position, the relay2410 may be opened so that current is unable to flow from the plug 2308to the outlet 2206. As another example, an application or programrunning on an access device may transmit a signal that causes the relay2410 to be opened or closed. For instance, an access application maydisplay a graphical interface on the access device that includes a powerbutton. The user may tap or otherwise select the power button, and theaccess application may send a communication signal (e.g., over a WiFinetwork) to the network device 2200 instructing the network device 2200to open or close the relay 2410.

The network device 2200 further includes flash memory 2420 and dynamicrandom access memory (DRAM) 2422. The flash memory 2420 may be used tostore instructions or code relating to an operating system, one or moreapplications, and any firmware. The flash memory 2420 may includenonvolatile memory so that any firmware or other program can be canupdated. In the event the network device 2200 loses power, informationstored in the flash memory 2420 may be retained. The DRAM 2422 may storevarious other types of information needed to run the network device2200, such as all runtime instructions or code.

The network device 2200 further includes a CPU/Radio 2418. The CPU/Radio2418 controls the operations of the network device 2200. For example,the CPU/Radio 2418 may execute various applications or programs storedin the flash memory 2420 and/or the dynamic random access memory (DRAM)2422. The CPU/Radio 2418 may also receive input from the varioushardware and software components, interpret the input, and perform oneor more functions in response to the input. As one example, theCPU/Radio 2418 may determine whether the power button 2202 has beenpressed, and determines whether the relay 2410 needs to be opened orclosed. The CPU/Radio 2418 may further perform all communicationsfunctions in order to allow the network device 2200 to communicate withother network devices, one or more gateways, a cloud network, and/or oneor more access devices. While the CPU and radio of the network device2200 are shown to be combined in the CPU/Radio 2418, one of ordinaryskill in the art will appreciate that, in some embodiments, the CPU andradio may be separately located within the network device 2200. Forexample, CPU circuitry may be situated at a separate location on acircuit board from the location of radio circuitry, the CPU circuitrymay be located on a different circuit board from the radio circuitry, orthe like.

The network device 2200 may communicate with other devices and/ornetworks via antenna 2424. For example, antenna 2424 may include a 2.4GHz antenna, a 5 GHz antenna, or the like, that can transmit and receiveWiFi communications signals. The antenna 2424 may include other types ofantennas that can communicate Bluetooth® signals, Zigbee® signals,Ultra-Wideband (UWB) signals, and/or the like. In some embodiments, thenetwork device 2200 may include multiple antennas for communicatingdifferent types of communication signals. As one example, the networkdevice 2200 may include both a 2.4 GHz antenna and a 5 GHz antenna.

The network device 2200 further includes a driver 2416, a switchingpower supply 2412, and a voltage regulator 2414. The driver 2416 mayinclude instructions or code that can be used to translate controlsignals or commands received from applications running on the DRAM 2422to commands that the various hardware components in the network device2200 can understand. In some embodiments, the driver 2416 may include anambient application running on the DRAM 2422. The switching power supply2412 may be used to transfer power from the outlet in which the plug2308 is connected to the various loads of the network device 2200 (e.g.,CPU/Radio 2418). The switching power supply 2412 may efficiently convertthe voltage and current characteristics of the electrical power to alevel that is appropriate for the components of the network device 2200.For example, the switching power supply 2412 may perform AC-DCconversion. In some embodiments, the switching power supply 2412 may beused to control the power that is relayed from the plug 2308 to theoutlet 2206. The voltage regulator 2414 may be used to convert thevoltage output from the switching power supply 2412 to a lower voltageusable by the CPU/Radio 2418. For example, the voltage regulator 2414may regulate the DC voltage from 5V to 3.3V.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in anon-transitory machine-readable storage medium, such as the flash memory2420 and/or the DRAM 2422. The network device 2200 can also comprisesoftware elements (e.g., located within the memory), including, forexample, an operating system, device drivers, executable libraries,and/or other code, such as one or more application programs, which maycomprise computer programs implementing the functions provided byvarious embodiments, and/or may be designed to implement methods and/orconfigure systems, as described herein. Merely by way of example, one ormore procedures described with respect to the processes discussed above,for example as described with respect to FIG. 2, may be implemented ascode and/or instructions executable by a computer (and/or a processorwithin a computer); in an aspect, then, such code and/or instructionscan be used to configure and/or adapt a general purpose computer (orother device) to perform one or more operations in accordance with thedescribed methods. Such functions or code may include code to performthe steps described above with respect to FIG. 2. The memory, such asthe flash memory 2420 and/or the DRAM 2422, may be a processor-readablememory and/or a computer-readable memory that stores software code(programming code, instructions, etc.) configured to cause aprocessor(s) within the CPU/Radio 2418 to perform the functionsdescribed. In other embodiments, one or more of the functions describedmay be performed in hardware.

A set of these instructions and/or code might be stored on anon-transitory machine-readable storage medium, such as the flash memory2420 and/or the DRAM 2422. In some cases, the storage medium might beincorporated within a computer system, such as the CPU/Radio 2418. Inother embodiments, the storage medium might be separate from a computersystem (e.g., a removable medium, such as a compact disc), and/orprovided in an installation package, such that the storage medium can beused to program, configure and/or adapt a general purpose computer withthe instructions/code stored thereon. These instructions might take theform of executable code, which is executable by the network device 2200and/or might take the form of source and/or installable code, which,upon compilation and/or installation on the network device 2200 (e.g.,using any of a variety of generally available compilers, installationprograms, compression/decompression utilities, etc.) then takes the formof executable code.

Substantial variations may be made in accordance with specificrequirements. For example, customized hardware might also be used,and/or particular elements might be implemented in hardware, software(including portable software, such as applets, etc.), or both. Further,connection to other access or computing devices such as networkinput/output devices may be employed.

It should be appreciated that the network device 2200 may have othercomponents than those depicted in FIGS. 22-24. Further, the embodimentshown in the figures are only one example of a network device that mayincorporate an embodiment of the invention. In some other embodiments,network device 2200 may have more or fewer components than shown in thefigure, may combine two or more components, or may have a differentconfiguration or arrangement of components.

FIG. 25 illustrates an example of an access device 2500. The accessdevice 2500 may include any human-to-machine interface with networkconnection capability that allows access to a network. For example, theaccess device 2500 may include a stand-alone interface (e.g., a cellulartelephone, a smartphone, a home computer, a laptop computer, a tablet, apersonal digital assistant (PDA), a computing device, a wearable devicesuch as a smart watch, a wall panel, a keypad, or the like), aninterface that is built into an appliance or other device (e.g.,television, refrigerator, security system, game console, browser, or thelike), a speech or gesture interface (e.g., Kinect™ sensor, Wiimote™, orthe like), an internet of things (IoT) device interface (e.g., anInternet enabled appliance such as a wall switch, a control interface,or the like). The access device 2500 includes hardware elements that canbe electrically coupled via a bus 2518 (or may otherwise be incommunication, as appropriate). In one embodiment, the bus 2518 can beused for the processor(s) 2502 to communicate between cores and/or withthe memory 2512. The hardware elements may include one or moreprocessors 2502, including without limitation one or moregeneral-purpose processors and/or one or more special-purpose processors(such as digital signal processing chips, graphics accelerationprocessors, and/or the like); one or more input devices 2516, which caninclude without limitation a camera, a mouse, a keyboard, a touchsensitive screen, a touch pad, a keypad, and/or the like; and one ormore output devices 2514, which can include, without limitation, adisplay, a printer, and/or the like.

The access device 2500 may include one or more wireless transceivers2506 connected to the bus 2518. The wireless transceiver 2506 may beoperable to receive wireless signals (e.g., signal 2510) via antenna2508. The wireless signal 2510 may be transmitted via a wirelessnetwork. In some embodiments, the wireless network may be any wirelessnetwork such as a wireless local area network (e.g., local area network100), such as WiFi, a Personal Access Network (PAN), such as Bluetooth®or Zigbee®, or a cellular network (e.g. a GSM, WCDMA, LTE, CDMA2000network). Wireless transceiver 2506 may be configured to receive variousradio frequency (RF) signals (e.g., signal 2510) via antenna 2508 fromone or more gateways, network devices, other access devices, cloudnetworks, and/or the like. Access device 2500 may also be configured todecode and/or decrypt, via the DSP 2504 and/or processor(s) 2502,various signals received from one or more gateways, network devices,other access devices, cloud networks, and/or the like.

The access device 2500 may further include (and/or be in communicationwith) one or more non-transitory machine-readable storage mediums orstorage devices (e.g., memory 2512), which can comprise, withoutlimitation, local and/or network accessible storage, and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, a solid-state storage device such as a random access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable and/or the like. Such storage devices may be configuredto implement any appropriate data storage, including without limitation,various file systems, database structures, and/or the like.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in memory 2512,such as RAM, ROM, FLASH, or disc drive, and executed by processor(s)2502 or DSP 2504. The access device 2500 can also comprise softwareelements (e.g., located within the memory 2512), including, for example,an operating system, device drivers, executable libraries, and/or othercode, such as one or more application programs, which may comprisecomputer programs implementing various functions. Memory 2512 may be anon-transitory machine-readable storage medium, processor-readablememory, and/or a computer-readable memory that stores the one or morecomputer-program products configured to cause the processor(s) 2502and/or DSP 2504 to perform the various functions. In other embodiments,the various functions described may be performed in hardware.

FIG. 26 illustrates an example of a server 2600. The server 2600includes hardware elements that can be electrically coupled via a bus2616 (or may otherwise be in communication, as appropriate). In oneembodiment, the bus 2616 can be used for the processor(s) 2602 tocommunicate between cores and/or with the memory 2612. The hardwareelements may include one or more processors 2602, including withoutlimitation one or more general-purpose processors and/or one or morespecial-purpose processors (such as digital signal processing chips,graphics acceleration processors, and/or the like), memory 2612, DSP2604, a wireless transceiver 2606, a bus 2616, and antenna 2608.Furthermore, in addition to the wireless transceiver 2606, server 2600can further include a network interface 2614 to communicate with anetwork (e.g., a local area network, a network of a preferred carrier,Internet, etc.).

The server 2600 may further include (and/or be in communication with)one or more non-transitory machine-readable storage mediums or storagedevices (e.g., memory 2612), which can comprise, without limitation,local and/or network accessible storage, and/or can include, withoutlimitation, a disk drive, a drive array, an optical storage device, asolid-state storage device such as a random access memory (“RAM”) and/ora read-only memory (“ROM”), which can be programmable, flash-updateableand/or the like. Such storage devices may be configured to implement anyappropriate data storage, including without limitation, various filesystems, database structures, and/or the like.

In various embodiments, functions may be stored as one or more one ormore computer-program products, such as instructions or code, in memory2612. The server 2600 can also comprise software elements (e.g., locatedwithin the memory), including, for example, an operating system, devicedrivers, executable libraries, and/or other code, such as one or moreapplication programs, which may comprise computer programs implementingthe functions provided by various embodiments, and/or may be designed toimplement methods and/or configure systems, as described herein. Merelyby way of example, one or more procedures described with respect to theprocesses discussed above may be implemented as code and/or instructionsexecutable by a computer (and/or a processor within a computer); in anaspect, then, such code and/or instructions can be used to configureand/or adapt a general purpose computer (or other device) to perform oneor more operations in accordance with the described methods. Suchfunctions or code may include code to perform the steps described abovewith respect to FIG. 2. The memory 2612 may be a non-transitorymachine-readable storage medium, processor-readable memory, and/or acomputer-readable memory that stores the one or more computer-programproducts configured to cause the processor(s) 2602 to perform thefunctions described. In other embodiments, one or more of the functionsdescribed may be performed in hardware.

A set of these instructions and/or code might be stored on anon-transitory machine-readable storage medium, such as the memory 2612.In some cases, the storage medium might be incorporated within acomputer system. In other embodiments, the storage medium might beseparate from a computer system (e.g., a removable medium, such as acompact disc), and/or provided in an installation package, such that thestorage medium can be used to program, configure and/or adapt a generalpurpose computer with the instructions/code stored thereon. Theseinstructions of one or more computer-program products might take theform of executable code, which is executable by the server 2600 and/ormight take the form of source and/or installable code, which, uponcompilation and/or installation on the server 2600 (e.g., using any of avariety of generally available compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

FIG. 27 illustrates an example of a gateway 2700. The gateway 2700 mayinclude a range extending device, a router, an access point, a modem,and/or any other device that provides network access among one or morecomputing devices and/or external networks. For example, the gateway2700 may include a router gateway with access point and routerfunctionality, and may further include an Ethernet switch and/or amodem. As another example, the gateway 2700 may include a rangeextending gateway that may be used to improve signal range and strengthwithin a network by taking an existing signal from another gateway(e.g., a router gateway, an access point, or the like) andrebroadcasting the signal to create a second logical network.

The gateway 2700 includes hardware elements that can be electricallycoupled via a bus 2718 (or may otherwise be in communication, asappropriate). In one embodiment, the bus 2718 can be used for theprocessor(s) 2702 to communicate between cores and/or with the memory2712. The hardware elements may include one or more processors 2702,including without limitation one or more general-purpose processorsand/or one or more special-purpose processors (such as digital signalprocessing chips, graphics acceleration processors, and/or the like);one or more input devices 2716, which can include without limitation oneor more buttons, a keyboard, a keypad, a touch sensitive screen, a touchpad, and/or the like; and one or more output devices 2714, which caninclude, without limitation, a display, light or sound indicators,and/or the like.

The gateway 2700 may include one or more wireless transceivers 2706 and2720 connected to the bus 2718. The wireless transceiver 2706 may beoperable to receive wireless signals (e.g., a wireless signal 2710) viaan antenna 2708. The wireless transceivers 2720 may be operable toreceive wireless signals (e.g., a wireless signal 2714) via an antenna2722. The wireless transceivers 2706 and 2720 may each include a WiFitransceiver radio designed to transmit and receive signals usingfrequencies of a specific frequency band, which may be referred toherein as “WiFi circuits.” For example, wireless transceiver 2706 mayinclude a 2.4 GHz WiFi circuit, and wireless transceiver 2720 mayinclude a 5 GHz WiFi circuit. Accordingly, the gateway 2700 may includea single WiFi circuit for a first WiFi frequency band, and a single WiFicircuit for a second WiFi frequency band. In some embodiments, thegateway 2700 may include multiple wireless transceivers (not shown) foreach available frequency band. The antennas 2708 and 2722 may includemultiple band antennas that can transmit and/or receive signals overdifferent frequency bands.

The gateway 2700 may further include radio frequency (RF) circuit 2726.In some embodiments, the wireless transceivers 2706 and 2720 may beintegrated with or coupled to the RF circuit 2726 so that the RF circuit2726 includes the wireless transceivers 2706 and 2720. In someembodiments, the wireless transceivers 2706 and 2720 and the RF circuit2726 are separate components. The RF circuit 2726 may include a RFamplifier that may amplify signals received over antennas 2708 and 2722.The RF circuit 2726 may also include a power controller that may be usedto adjust signal amplification by the RF amplifier. The power controllermay be implemented using hardware, firmware, software, or anycombination thereof.

The wireless signals 2710 and 2724 may be transmitted via a wirelessnetwork. In some embodiments, the wireless network may be any wirelessnetwork such as a wireless local area network (e.g., local area network100), such as WiFi™, a Personal Access Network (PAN), such as Bluetooth®or Zigbee®, or a cellular network (e.g. a GSM, WCDMA, LTE, CDMA2000network). Wireless transceivers 2706 and 2720 may be configured toreceive various radio frequency (RF) signals (e.g., signals 2710 and2724) via antennas 2708 and 2724, respectively, from one or more othergateways, access devices, network devices, cloud networks, and/or thelike. Gateway 2700 may also be configured to decode and/or decrypt, viathe DSP 2704 and/or processor(s) 2702, various signals received from oneor more gateways, network devices, cloud networks, and/or the like.

The gateway 2700 may include a power supply (not shown) that can powerthe various components of the gateway 2700. The power supply may includea switch-mode power supply, a linear power supply, a push-pull powersupply, or any other suitable type of power supply. In some embodiments,the gateway 2700 may include multiple power supplies. For example, aswitch-mode power supply may be used to condition input power, and alinear power supply may be used to power the RF circuit 2726. The powersupply may be configured to operate over various ranges of appropriateinput voltages.

The gateway 2700 may further include (and/or be in communication with)one or more non-transitory machine-readable storage mediums or storagedevices (e.g., memory 2712), which can comprise, without limitation,local and/or network accessible storage, and/or can include, withoutlimitation, a disk drive, a drive array, an optical storage device, asolid-state storage device such as a random access memory (“RAM”) and/ora read-only memory (“ROM”), which can be programmable, flash-updateableand/or the like. Such storage devices may be configured to implement anyappropriate data storage, including without limitation, various filesystems, database structures, and/or the like.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in memory 2712,such as RAM, ROM, FLASH, or disc drive, and executed by processor(s)2702 or DSP 2704. The gateway 2700 can also comprise software elements(e.g., located within the memory 2712), including, for example, anoperating system, device drivers, executable libraries, and/or othercode, such as one or more application programs, which may comprisecomputer programs implementing the functions provided by variousembodiments, and/or may be designed to implement methods and/orconfigure systems, as described herein. Merely by way of example, one ormore procedures described with respect to the processes discussed above,for example as described with respect to FIG. 14, may be implemented ascode and/or instructions executable by a computer (and/or a processorwithin a computer); in an aspect, then, such code and/or instructionscan be used to configure and/or adapt a general purpose computer (orother device) to perform one or more operations in accordance with thedescribed methods. Such functions or code may include code to performthe steps described above with respect to FIG. 14. The memory 2712 maybe a non-transitory machine-readable storage medium, processor-readablememory, and/or a computer-readable memory that stores the one or morecomputer-program products configured to cause the processor(s) 2702 toperform the functions described. In other embodiments, one or more ofthe functions described may be performed in hardware.

A set of these instructions and/or code might be stored on anon-transitory machine-readable storage medium, such as the memory 2712.In some cases, the storage medium might be incorporated within acomputer system. In other embodiments, the storage medium might beseparate from a computer system (e.g., a removable medium, such as acompact disc), and/or provided in an installation package, such that thestorage medium can be used to program, configure and/or adapt a generalpurpose computer with the instructions/code stored thereon. Theseinstructions of one or more computer-program products might take theform of executable code, which is executable by the gateway 2700 and/ormight take the form of source and/or installable code, which, uponcompilation and/or installation on the gateway 2700 (e.g., using any ofa variety of generally available compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

Substantial variations may be made in accordance with specificrequirements. For example, customized hardware might also be used,and/or particular elements might be implemented in hardware, software(including portable software, such as applets, etc.), or both. Further,connection to other access or computing devices such as networkinput/output devices may be employed.

In the foregoing specification, aspects of the invention are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

In the foregoing description, for the purposes of illustration, methodswere described in a particular order. It should be appreciated that inalternate embodiments, the methods may be performed in a different orderthan that described. It should also be appreciated that the methodsdescribed above may be performed by hardware components or may beembodied in sequences of machine-executable instructions, which may beused to cause a machine, such as a general-purpose or special-purposeprocessor or logic circuits programmed with the instructions to performthe methods. These machine-executable instructions may be stored on oneor more machine readable mediums, such as CD-ROMs or other type ofoptical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magneticor optical cards, flash memory, or other types of machine-readablemediums suitable for storing electronic instructions. Alternatively, themethods may be performed by a combination of hardware and software.

Where components are described as being configured to perform certainoperations, such configuration can be accomplished, for example, bydesigning electronic circuits or other hardware to perform theoperation, by programming programmable electronic circuits (e.g.,microprocessors, or other suitable electronic circuits) to perform theoperation, or any combination thereof.

While illustrative embodiments of the application have been described indetail herein, it is to be understood that the inventive concepts may beotherwise variously embodied and employed, and that the appended claimsare intended to be construed to include such variations, except aslimited by the prior art.

What is claimed is:
 1. A method, comprising: establishing, at anexisting network device on a network, a connection between the existingnetwork device and a new network device associated with the network;receiving identification information, wherein the identificationinformation includes information identifying the new network device;receiving a communication including an indication that an additional newnetwork device is connected to the new network device; transmitting acommunication, including a request for additional identificationinformation associated with the additional new network device; receivingadditional identification information, where the additionalidentification information includes information identifying theadditional new network device; analyzing the identification informationand the additional identification information to determine acharacteristic associated with the new network device and the additionalnew network device; establishing a network device group, wherein thenetwork device group includes network devices associated with thecharacteristic, and wherein the network device group includes the newnetwork device and the additional new network device; and transmittingthe identification information of the devices in the network devicegroup, wherein when the identification information of the devices in thenetwork device group is received, the identification informationfacilitates generating one or more authorization queries to authorizethe new network devices in the network device group to join the network,and wherein the new network devices in the network device group join thenetwork using the one or more authorization queries.
 2. The method ofclaim 1, further comprising: receiving, at the existing network deviceon the network, a communication, wherein the communication includes anindication that the new network device is associated with the network,and wherein the network includes an access device and a gateway, thegateway having previously provided the existing network device withaccess to the network; receiving an indication that the new networkdevice has generated a setup access point; and establishing a connectionwith the setup access point of the new network device.
 3. The method ofclaim 1, wherein the identification information and the additionalidentification information are transmitted simultaneously.
 4. The methodof claim 1, further comprising: generating one or more authorizationqueries to authorize network devices in the network device group; andtransmitting the authorization queries.
 5. The method of claim 4,further comprising: receiving one or more responses to the one or moreauthentication queries; and transmitting network credentialscorresponding to each of the responses to the one or more authenticationqueries, wherein network credentials facilitate joining the network. 6.The method of claim 1, wherein the identification informationidentifying the new network device and the additional identificationinformation identifying the additional new network device are receivedat the same time.
 7. The method of claim 1, further comprising:transmitting the one or more authorization queries, wherein receivingauthorization queries facilitates displaying the identificationinformation or the additional identification information.
 8. A computingdevice, comprising: one or more processors; and a memory havinginstructions stored thereon, which when executed by the one or moreprocessors, cause the computing device to perform operations including:establishing, at an existing network device on a network, a connectionbetween the existing network device and a new network device associatedwith the network; receiving identification information, wherein theidentification information includes information identifying the newnetwork device; receiving a communication including an indication thatan additional new network device is connected to the new network device;transmitting a communication, including a request for additionalidentification information associated with the additional new networkdevice; receiving additional identification information, where theadditional identification information includes information identifyingthe additional new network device; analyzing the identificationinformation and the additional identification information to determine acharacteristic associated with the new network device and the additionalnew network device; establishing a network device group, wherein thenetwork device group includes network devices associated with thecharacteristic, and wherein the network device group includes the newnetwork device and the additional new network device; and transmittingthe identification information of the devices in the network devicegroup, wherein when the identification information of the devices in thenetwork device group is received, the identification informationfacilitates generating one or more authorization queries to authorizethe new network devices in the network device group to join the network,and wherein the new network devices in the network device group join thenetwork using the one or more authorization queries.
 9. The computingdevice of claim 8, further comprising instructions, which when executedby the one or more processors, cause the computing device to performoperations including: receiving, at the existing network device on thenetwork, a communication, wherein the communication includes anindication that the new network device is associated with the network,and wherein the network includes an access device and a gateway, thegateway having previously provided the existing network device withaccess to the network; receiving an indication that the new networkdevice has generated a setup access point; and establishing a connectionwith the setup access point of the new network device.
 10. The computingdevice of claim 8, wherein the identification information and theadditional identification information are transmitted simultaneously.11. The computing device of claim 8, further comprising instructions,which when executed by the one or more processors, cause the computingdevice to perform operations including: generating one or moreauthorization queries to authorize network devices in the network devicegroup; and transmitting the authorization queries.
 12. The computingdevice of claim 11, further comprising instructions, which when executedby the one or more processors, cause the computing device to performoperations including: receiving one or more responses to the one or moreauthentication queries; and transmitting network credentialscorresponding to each of the responses to the one or more authenticationqueries, wherein network credentials facilitate joining the network. 13.The computing device of claim 8, wherein the identification informationidentifying the new network device and the additional identificationinformation identifying the additional new network device are receivedat the same time.
 14. The computing device of claim 8, furthercomprising instructions, which when executed by the one or moreprocessors, cause the computing device to perform operations including:transmitting the one or more authorization queries, wherein receivingauthorization queries facilitates displaying the identificationinformation or the additional identification information.
 15. Anon-transitory computer-readable storage medium having instructionsstored thereon, which when executed by a computing device, cause thecomputing device to: establish, at an existing network device on anetwork, a connection between the existing network device and a newnetwork device associated with the network; receive identificationinformation, wherein the identification information includes informationidentifying the new network device; receive a communication including anindication that an additional new network device is connected to the newnetwork device; transmit a communication, including a request foradditional identification information associated with the additional newnetwork device; receive additional identification information, where theadditional identification information includes information identifyingthe additional new network device; analyze the identificationinformation and the additional identification information to determine acharacteristic associated with the new network device and the additionalnew network device; establish a network device group, wherein thenetwork device group includes network devices associated with thecharacteristic, and wherein the network device group includes the newnetwork device and the additional new network device; and transmit theidentification information of the devices in the network device group,wherein when the identification information of the devices in thenetwork device group is received, the identification informationfacilitates generating one or more authorization queries to authorizethe new network devices in the network device group to join the network,and wherein the new network devices in the network device group join thenetwork using the one or more authorization queries.
 16. Thenon-transitory computer-readable storage medium of claim 15, furthercomprising instructions configured to cause the computing device to:receive, at the existing network device on the network, a communication,wherein the communication includes an indication that the new networkdevice is associated with the network, and wherein the network includesan access device and a gateway, the gateway having previously providedthe existing network device with access to the network; receive anindication that the new network device has generated a setup accesspoint; and establish a connection with the setup access point of the newnetwork device.
 17. The non-transitory computer-readable storage mediumof claim 15, wherein the identification information and the additionalidentification information are transmitted simultaneously.
 18. Thenon-transitory computer-readable storage medium of claim 15, furthercomprising instructions configured to cause the computing device to:generate one or more authorization queries to authorize network devicesin the network device group; and transmit the authorization queries. 19.The non-transitory computer-readable storage medium of claim 18, furthercomprising instructions configured to cause the computing device to:receive one or more responses to the one or more authentication queries;and transmit network credentials corresponding to each of the responsesto the one or more authentication queries, wherein network credentialsfacilitate joining the network.
 20. The non-transitory computer-readablestorage medium of claim 15, wherein the identification informationidentifying the new network device and the additional identificationinformation identifying the additional new network device are receivedat the same time.
 21. The non-transitory computer-readable storagemedium of claim 15, further comprising instructions configured to causethe computing device to: transmit the one or more authorization queries,wherein receiving authorization queries facilitates displaying theidentification information or the additional identification information.